June 6, 2016 at 10:43 am
Hello All,
We have a TSQL script that is run out of hours to restore a 88GB database, when the job completes successfully the said database is restored within 8 minutes.
However when I manually restore the database during work hours by running the script as a SSMS - Query, it takes 30 to 35 minutes to do the restore. What could be causing the restore to take 4 to 5 times longer?
Is there a cost involved when running a restore from SSMS - Query manually and from Client workstation?
Its a strange issue that I have not been able to find answers for hence any advise/help welcome.
June 6, 2016 at 11:24 am
Disk IO at a guess- when run out of hours it isn't as constrained as when run during working hours and has to compete with other processes for IO and other resources.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply