January 31, 2011 at 2:16 pm
Hey there. I've been trying to restore a database (size is around 500GB), from a local drive on my box (F) to another local drive on my box (E). However it is taking quite a bit of time - left Friday nite and came back Monday morning to it still at 0%! I killed that, did some research, added more tempDB files with one file on the F drive (a 1TB size drive) left to autogrow. I also created a blank db and am currently restoring to that db with REPLACE. However, it's still saying 0%. In the SQL Activity monitor, it's showing wait types of PREEMPTIVE_OS_WRITEFILEGATHER and ASYNC_IO_COMPLETE. After researching these, I'm wondering if there is an issue with sqlserver.exe (installed on C drive) accessing the backup file on F drive and or copying to E drive? I'm new to Windows 7 and keep having to "Allow Access" to programs I've installed to run so I'm not sure if this is the issue or not? Any advise would be great! THanks!!!
System: Windows 7, 8GB RAM, 8 CPUS, 2 extra TB drives
SQL Server: 2008R2 Developer
January 31, 2011 at 2:19 pm
btw - forgot to mention, service is running as Network Service
January 31, 2011 at 2:34 pm
Just a guess, but I am thinking that you don't have instant initialization enabled and that is causing the time delay. Without that, SQL Server has to zero initialize both the data and log files.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 31, 2011 at 3:07 pm
You were correct, I had not set that up....until now.... 😉 Brilliant! Thank you!! it's already at 10% after setting that up! Truly appreciate it!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply