December 14, 2006 at 4:39 pm
Good day to all,
I'm using a 3rd party backup solution. It has been running fantastic for about 3 weeks. Recently, a set a restores has gone from taking about 4 hours to about 12 hours. After looking through many log files, we are seeing a ton of VDI timeouts. After watching perfmon and taskmanager I noticed that the when the physical mdf and ldf files are being created, our write disk queue length is low - goes to 0 fro multiple seconds. There are times when there is no activity. I am watching the sqlserv.exe process and the io writes in task manager to come to this conclusion. As soon as the physical files are created and the 3rd party backup begins decompressing the database, the write disk queue length go much higher > 40 and the sqlserv.exe processes is always writing something (again watching task manager and the io writes column.)
I know that there is not a lot of activity on this box except for restoring the databases.
Is there a way to force sqlsevr.exe to increase the write I/Os it tries to do while it’s creating the physical files? I'm going to bump up the priority on sql server tomorrow, hopefully that will help this. We have not changed anything on the server.
Environment:
OS - Server 2000 sp4
SQL Version - 8.00.2187
December 18, 2006 at 8:00 am
This was removed by the editor as SPAM
December 21, 2006 at 3:43 pm
There is nothing in sql 2000 you can do to speed up the creation of the data files to disk on a new restore or restore with replace. the deal is sql is zeroing out the files and it is a single threaded operation. creating multiple files may help.
2005 doesn't zero the files out so restore times are much faster on a new restore or restore with replace.
Wes
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply