I just watched an on demand webcast for SharePoint which uses SQL as the back
end database. The Microsoft presenter talked about using an explorer tool to
open sql backup files and extracting data. Does anybody know what tool he is
talking about? Supposedly, Microsoft uses this tool to recover a document
that was deleted on a SharePoint site but was in a full sql backup the
previous night. This is their solution to file level recovery. I've got to
have it.
--
Will RobinsonI've listed three such tools on my link page:
http://www.karaszi.com/SQLServer/links.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"WillAva" <WillAva@.discussions.microsoft.com> wrote in message
news:A561982D-225D-49EE-879B-BAF5D500D52D@.microsoft.com...
>I just watched an on demand webcast for SharePoint which uses SQL as the back
> end database. The Microsoft presenter talked about using an explorer tool to
> open sql backup files and extracting data. Does anybody know what tool he is
> talking about? Supposedly, Microsoft uses this tool to recover a document
> that was deleted on a SharePoint site but was in a full sql backup the
> previous night. This is their solution to file level recovery. I've got to
> have it.
>
> --
> Will Robinson
Showing posts with label back. Show all posts
Showing posts with label back. Show all posts
Thursday, March 22, 2012
Sunday, March 11, 2012
Database disconnected from server
SQL Server 2000
Our server froze up and forced a reboot.
When the server came back online, the database was
no longer listed in EM as a database but the datafiles
themselves still exist. In addition, it appears that SQL
Server may still be "holding on" to the data files since when
I try to delete them, the operating system tells me they
can't be deleted.
I'd like to just reattach the datafiles to the server
and have the database reappear. How can I do this?Try to stop SQL Server service move the .MDF and .LDF to
other folder and then start SQL Server again. Move back
SQL Server files to their original folders and then
reattach the database.
Cesar Kubo
>--Original Message--
>SQL Server 2000
>Our server froze up and forced a reboot.
>When the server came back online, the database was
>no longer listed in EM as a database but the datafiles
>themselves still exist. In addition, it appears that
SQL
>Server may still be "holding on" to the data files since
when
>I try to delete them, the operating system tells me they
>can't be deleted.
>I'd like to just reattach the datafiles to the server
>and have the database reappear. How can I do this?
>
>.
>|||Hi Simon,
Happy New Year and thank you for using MSDN Newsgroup! It's my pleasure to
assist you with your issue.
From the information you provided, your SQL Enterprise Manager cannot get
the information of the database, but its MDF and LDF is still in you disk.
You cannot delete them because the system informed you that them are still
in use. You wonder if you can reattatch this files so that the SQL Server
Enterprise Manager could show the database and manage the database, right.
From my experience, in most cases, it is SQL Service that is still using
this file. You can stop the SQL Server Service.
Then, restart you SQL Service, and in you Query Analyzer, run the following
batches:
exec sp_attach_db @.dbname='your_database_name'
@.filename1='MDF_file' --for example: 'c:\test.mdf'
@.filename2='LDF_file' --for example: 'c:\test_log.ldf'
If you do not want to use the former log file, run the following:
exec sp_attatch_single_file_db @.dbname='your_database_name'
@.physname='MDF_file' --for example: 'c:\test.mdf'
Note: The system will create a new log file, but all the information in the
old log file will be lost.
Hoping this information will be helpful in solving your problem. If you
still have questions, please feel free to post new message here and I am
ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Our server froze up and forced a reboot.
When the server came back online, the database was
no longer listed in EM as a database but the datafiles
themselves still exist. In addition, it appears that SQL
Server may still be "holding on" to the data files since when
I try to delete them, the operating system tells me they
can't be deleted.
I'd like to just reattach the datafiles to the server
and have the database reappear. How can I do this?Try to stop SQL Server service move the .MDF and .LDF to
other folder and then start SQL Server again. Move back
SQL Server files to their original folders and then
reattach the database.
Cesar Kubo
>--Original Message--
>SQL Server 2000
>Our server froze up and forced a reboot.
>When the server came back online, the database was
>no longer listed in EM as a database but the datafiles
>themselves still exist. In addition, it appears that
SQL
>Server may still be "holding on" to the data files since
when
>I try to delete them, the operating system tells me they
>can't be deleted.
>I'd like to just reattach the datafiles to the server
>and have the database reappear. How can I do this?
>
>.
>|||Hi Simon,
Happy New Year and thank you for using MSDN Newsgroup! It's my pleasure to
assist you with your issue.
From the information you provided, your SQL Enterprise Manager cannot get
the information of the database, but its MDF and LDF is still in you disk.
You cannot delete them because the system informed you that them are still
in use. You wonder if you can reattatch this files so that the SQL Server
Enterprise Manager could show the database and manage the database, right.
From my experience, in most cases, it is SQL Service that is still using
this file. You can stop the SQL Server Service.
Then, restart you SQL Service, and in you Query Analyzer, run the following
batches:
exec sp_attach_db @.dbname='your_database_name'
@.filename1='MDF_file' --for example: 'c:\test.mdf'
@.filename2='LDF_file' --for example: 'c:\test_log.ldf'
If you do not want to use the former log file, run the following:
exec sp_attatch_single_file_db @.dbname='your_database_name'
@.physname='MDF_file' --for example: 'c:\test.mdf'
Note: The system will create a new log file, but all the information in the
old log file will be lost.
Hoping this information will be helpful in solving your problem. If you
still have questions, please feel free to post new message here and I am
ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
database disappearence
All of a sudden all the databases under the SQL Server Enterprise Manager have disappeared. Any idea why and how to get them back? I 'm on SQL 2000 with SP3Damn Miracle thing again....
Close and restart EM...What happens?|||That sure is a miracle brett :)|||I though miracles were supposed to be good things? Sounds more like a voodoo curse to me.
Try waving a dead chicken over it.
Close and restart EM...What happens?|||That sure is a miracle brett :)|||I though miracles were supposed to be good things? Sounds more like a voodoo curse to me.
Try waving a dead chicken over it.
Labels:
back,
database,
databases,
disappeared,
disappearence,
enterprise,
idea,
manager,
microsoft,
mysql,
oracle,
server,
sql,
sudden
Friday, February 24, 2012
database design for periodic update
Hi. I have an application running on local machines at different geographic locations, that need to update data (and pick some info back) to a central server at the end of the day (receiving data from all locations).
Data volume can be 500 records / day, nearly 2 MB.
I am not sure if this can be called distributed database.
I plan to use SQL Server on the central server and am undecided on whether to use MS Access / SQL server. I will be using VB for the application.
What application technology and database technology (and data transfer) would be ideal?
Thanks.I would think that SQL Server would be the most ideal. You could set up separate ACCESS DSN (for your various clients to upload their MS Access database updates to), then use DTS within SQL Server to pull data from these various datasources.
What I would recommend is the following (in terms of the DTS structure, easiest, not the most jazzy or seamless approach, but it may work, of course, the other option is writing a stored procedure to either UPDATE or INSERT data into your centralized database):
1) Delete all data from central database.
2) Append data from client#1
3) Append data from client#2
4) Append data from client#3
etc...
Data volume can be 500 records / day, nearly 2 MB.
I am not sure if this can be called distributed database.
I plan to use SQL Server on the central server and am undecided on whether to use MS Access / SQL server. I will be using VB for the application.
What application technology and database technology (and data transfer) would be ideal?
Thanks.I would think that SQL Server would be the most ideal. You could set up separate ACCESS DSN (for your various clients to upload their MS Access database updates to), then use DTS within SQL Server to pull data from these various datasources.
What I would recommend is the following (in terms of the DTS structure, easiest, not the most jazzy or seamless approach, but it may work, of course, the other option is writing a stored procedure to either UPDATE or INSERT data into your centralized database):
1) Delete all data from central database.
2) Append data from client#1
3) Append data from client#2
4) Append data from client#3
etc...
Subscribe to:
Posts (Atom)