April 16, 2013 at 2:33 pm
Simply put, the data file size is larger than the max file size.
Data file size = 105 Mb, Max file size = 100 Mb.
SQL Server 2008 R2 - SP2, Full mode, compatibility level 90.
We can increase the max file size, but the question lingers...how did this occur?
Advice/experience appreciated, thanks.
April 16, 2013 at 2:54 pm
What is the growth increment for the file (if it's auto-grow). Could be that the multiples of the growth increment onto the original size forced the last expansion to go over 100MB. Just a guess.
April 16, 2013 at 2:58 pm
Auto growth set to 10 Mb
April 16, 2013 at 3:03 pm
What was the original file size? if it was 85 and the system had to take 2 expansions along the way, the last 10 it grabbed might have pushed the size above the max. I might have assumed the expected behavior would be to either take all it could of the last 10 up to the max size, or declare itself full since it couldn't take the full 10 allocation without passing the max size. The actual behavior might be to take the full 10, even if it crosses the max size line and declare itself full if it has to take another allocation of 10 later on.
I haven't tested that, but it would explain the observed situation.
April 16, 2013 at 4:22 pm
Not sure about the initial size, as I inherited the database and there's no documentation.
However, your explanation does make sense.
Thank you for the prompt response.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply