Awful performance when restoring dB | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Awful performance when restoring dB

Hi there, newb here, so tip of the hat to y’all, and I’ll try to keep it nice. When I go to do a vanilla dB restore in EntMan (just right click on dB / all tasks / restore database), it takes ages to come up with the Restore Database dialog box. If I’m running EntMan on my client PC, it takes about 7 mins.(2.8 GHz P4)
If I’m running EntMan on the server, it takes about 7 mins.(4*2 GHz Xeon) While I’m waiting for the Restore Database dialog to present, I’m seeing mmc.exe running real hard. But what processing can it be doing? All it is looking for are the backup sets and log sets! The dB itself is small – only about 7 Gb. ?, ?, and thrice ? [edit] I should mention that once the restore gets going, the time taken to restore is just fine – it’s only the displaying of the Restore Database dialog that drags.[/edit]
I never perform such RESTORE operations using flaky Enterprise Manager, its recommended to use Query analyzer with RESTORE statement in order to get easy results. I suspect it could be trouble with SQL client tools installed on that box. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I know, I know, I’m a lamer for using EntMan. I really should use QA for this sort of thing. Point taken<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br /><br />But I doubt it’s the client install, because it’s slow whether I run EM client side or server side – 2 different installs. It may be worth mentioning that we log ship like crazy off this dB – we ship logs every 5 mins. Could this be responsible in some obscure way?
Its common time-factor delay when you try it(RESTORE) from Enterprise Manager and it may have adverse affect on server as well, so never used so. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>