March 4, 2010 at 6:02 pm
TheSQLGuru (3/4/2010)
Sometimes just reading forums regularly helps to gain knowledge !
Actually you didn't need to read this forum to gain knowledge. That stuff you watched has been on the web for a long time now. 😀
I agree .. but sometimes the obvious remains obscure ! 🙂
\\K
______________________________________________________________________________________________________________________________________________________________________________________
HTH !
Kin
MCTS : 2005, 2008
Active SQL Server Community Contributor 🙂
March 4, 2010 at 6:06 pm
And sometimes the sign posts get lost..... all we can do is but try ...
😛
April 14, 2012 at 5:01 am
[p]Server reboot is not an easy job as it looks like. You should be very cautious while rebooting your SQL server because any minor mistake can corrupt your whole SQL database, i think the same happened with you and you had a list of corrupted and suspected files which you tried to fix with some coding but the problem is not resolved because these coding don't provide a proper solution. You need to have a commercial tool that can fix the errors of your corrupted SQL database.[/p]
[p]You can get more information about the management tool from http://www.mssqlrepair.n.nu/repair-corrupt-ms-sql-database.html, it will help you to repair the corrupted files.[/p]
[p]And one more thing I would like suggest you that please don't reboot your MS SQL Server incautiously next time.[/p]
August 9, 2016 at 9:26 am
If you need to manually restore an SQL Database in Management Studio you can follow the instructions below for the version of SQL Server running on your server.
SQL 2012:
1. Log onto SQL Server Management Studio.
2. Navigate to the database you wish to restore.
3. Right Click > Tasks > Restore > Database.
4. Once on the General tab set the source to Device > Select Backup Device > Add > Navigate to the .bak file you're restoring to.
5. Ensure the Destination Database is the correct one.
6. Select the Options tab.
7. Check "Overwrite the existing database (WITH REPLACE)" and "Close existing connections to destination database".
8. Uncheck "Take tail-log backup before restore".
9. Click OK.
August 9, 2016 at 9:33 am
6 year old thread, and a completely irrelevant reply to boot.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 10, 2024 at 3:39 pm
This was removed by the editor as SPAM
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply