Autogrow of file 'test_Data' in database 'test' cancelled or timed out after 29641 ms. Use ALTER DATABASE to set a smaller FILEGROWTH or to set a new size.
It's trying to grow by 3.7 Gigs in one chunk. If the drives are busy this will take longer than SQL will allow for. Change the growth setting to 500 Megs and you shouldn't have any problems. This will give you a good size growth, that SQL won't have to wait very long to grow so the growth time shouldn't effect performance.
You certainly know more about this stuff than I do. I was wondering if a fragmented drive would take longer to grow a database than a defragmented drive. Any thoughts?
-George
Strong and bitter words indicate a weak cause. - Fortune cookie wisdom
Probably a little bit, but only by seconds. When the drive is fragmented it will write some of the file, then SQL has to wait for the drive head to get to the next free spot on the drive.
The reason it takes so long for SQL to extend the file is that after it extends the file, it writes zeros to the new part of the file. That's the part that takes the time.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.