A client whom I often help with Comprehensive Database Performance Health Check recently reached out to me with an interesting problem about Source Database in Restoring State.
My client had used SSMS to restore the database based on the original database. After doing a restore, he was very surprised as he was able to successfully use the new database but the original database in the restoring state. It was very much a surprise to him as he had just used a database as a source and it went into restoring state.
Well, this happens when you forget to tick the tail backup option in the SSMS wizard. The fix of this situation is very simple. Just run the following statement and it will immediately fix your source database.
RESTORE DATABASE SourceDBName WITH RECOVERY
Here are my few recent videos and I would like to know what is your feedback about them. Do not forget to subscribe SQL in Sixty Seconds series. I hope you appreciate learning about the Last 5 SQL in Sixty Seconds Video.
- Generate Script of SQL Server Objects – SQL in Sixty Seconds #184
- Prevent Unauthorized Index Modifications – SQL in Sixty Seconds #183
- MAX Columns Ever Existed in Table – SQL in Sixty Seconds #182
- Tuning Query Cost 100% – SQL in Sixty Seconds #181
- Queries Using Specific Index – SQL in Sixty Seconds #180
- Read Only Tables – Is it Possible? – SQL in Sixty Seconds #179
- One Scan for 3 Count Sum – SQL in Sixty Seconds #178
- SUM(1) vs COUNT(1) Performance Battle – SQL in Sixty Seconds #177
- COUNT(*) and COUNT(1): Performance Battle – SQL in Sixty Seconds #176
If you have any questions, you can always reach out to me on Twitter.
Reference: Pinal Dave (http://blog.SQLAuthority.com)