First all our autogrow settings are either turned off or the file size is set to the max autogrow size. I guess same difference as I came in after the setup.
Although I've never had this problem, I've been looking for an answer to a possible condition: I need my file to grow for example a tiny amount, say 100 MB for a insert to happen. However my autogrow is set to say 500MB. The disk has 450 MB available. What would happen in that scenario. And just say this insert happens once in a while at night, so I had no idea that it was going to happen, so I couldn't or didn't pre grow the file.
I'm really just curious about how sql server would handle this.
Best Answer
SQL server would handle this aborting your transaction and throwing the following error:
I got this message from a test where I designed a scenario close enough to what you described:
I placed the database
MyDB
in a small disk with 100MB in size. Inserts in the tabledbo.TextTable
worked fine until the file needed to grow (500MB) in order to acomodate more data, but failed due to the lack of space in the disk.Microsoft says that