August 11, 2015 at 8:28 am
I have a database on 2014 ent edition. When I go to restore the database via ssms (right click > tasks> restore > database) I don't get a wizard window at all it just does nothing. When I use 2008 ssms I get the wizard with the whole log chain built. On the same 2014 instance if I do the same for another database I get the wizard with its log chain? If I chose the other database in that wizard in the source database setting it just spins and spins trying to build the restore plan? Only difference between the two it I do have log shipping enabled on the broken database. Any ideas? I think I am service packed but will check that as well. thanks for any help.
August 12, 2015 at 3:11 am
Hi,
Have you tried to attach a SQL Server Profiler so you can see what is doing while you open the restore window? It maybe give you some hint.
Sorry for not been more helpful.
August 12, 2015 at 5:18 am
Something must be wrong with your SQL Server Management Studio then. I just validated that it does exactly the same thing on my system as it has always done, open up the Database Restore GUI (not quite a Wizard). Try it connected to a different server just to validate it's not something up with the server itself. Then try uninstalling and reinstalling SSMS. You could also try the stand-alone SSMS install that they have available now. Read more about it here. You should see the GUI though. It's still there.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 12, 2015 at 5:20 am
JManuelN (8/12/2015)
Hi,Have you tried to attach a SQL Server Profiler so you can see what is doing while you open the restore window? It maybe give you some hint.
Sorry for not been more helpful.
I strongly advise against using the Profiler GUI on a production system. It's actually somewhat dangerous. Since we're working in a SQL Server version greater than 2008R2, the Extended Events GUI is absolutely the preferred mechanism for observing system behavior.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 12, 2015 at 10:09 am
Thanks for the replys everyone. I have tried from different versions of ssms 2014 and the same behavior exists. If I use 2008r2 it sees the revoceryplan and the dialog opens. I dont understand extended events enough to trouble shoot. I did look and the instance needs sp1 as well as a cu. Could that fix the issue?
August 12, 2015 at 10:58 am
mlorek (8/12/2015)
Thanks for the replys everyone. I have tried from different versions of ssms 2014 and the same behavior exists. If I use 2008r2 it sees the revoceryplan and the dialog opens. I dont understand extended events enough to trouble shoot. I did look and the instance needs sp1 as well as a cu. Could that fix the issue?
It's possible. Also, make sure you apply service packs and cumulative updates to your SSMS gui if you have a stand-alone install.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 13, 2015 at 11:12 am
What level of SQL Server 2014 are you at? RTM, CU, SP1? select @@version will give you that if you don't know.
August 14, 2015 at 8:19 am
Thanks Everyone for the help. It turned out to be very simple, but still a little uneasy about the situation. Our maintenance was taking tlog backups and sending them to a network share every 15 minutes. I was for some reason keeping 172 hours of them. When the restore gui launched it tried to build the restore plan against the large amounts of backup sets is what I can deduce. I was never patient enough to let it finish. I took a full backup of the database and ran one tlog out and it would rebuild the backup set, still took a little time. All I can think is the extra backup up tlogs were confusing the chaining. Thanks again for all the help.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply