Unexpected Growth in one DB

  • I had a problem similar to this recently, and the issue turned out to be that the autogrowth setting was set to 5000% rather than 5000M. I believe that this is a known issue with SS2005 SP1, wherein the number you supply for "Meg" gets interpreted and set as "percent." As you might imagine, the first time that growth was attempted, we instantly ran out of disk space. Worth checking.

Viewing post 16 (of 15 total)

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