DB autogrew when it should not have

Question

DB autogrew when it should not have

Vik Nat

Hall of Fame

Points: 3930
More actions
September 15, 2003 at 9:15 am

#76052

I have encountered something very strange this weekend, which I have not been able to find an answer for yet. I have a Prod DB that was around 36 GB in size with about 5 GB of free space, so 31 GB used and 5 GB free space allocated to the MDF. After the reindexing job this weekend, looks like the DB acquired an additional approx 4GB of space. Now I have a DB that is 40GB in size with of which 9GB is free. I am not sure how that happened considering I have the autogrow set to 10%. Before I begin thinking of shrinking the DB( Which is always fun :), I'd like to try and get a reason as to why this happened. If anyone has encountered a similiar problem, insight to this issue is greatly appreciated

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Vladan SSC-Insane Points: 22072 More actions · Answer 1

Hi,

if you have the Autogrow set to 10%, then it seems to me that it grew just as much as it is allowed to in one jump - original size 36GB, 10% is 3.6GB - that makes it almost 40GB now. Apparently during reindexing or some other job your database ran out of space (used the free 5GB and it was not enough) and expanded by the amount set in Autogrow... Or did I miss something?

Our DB was 25GB two years ago and has grown to 90GB over the time, so I'm not at all surprised at what happened with your Prod. DB .

Edited by - Vladan on 09/15/2003 09:36:58 AM