Sunday, February 19, 2012

file growth problem in 2005

I just had a problem similar to the one in this post on the MSDN forum
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/Sho...71057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 10
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!
Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same:
http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
John
"mp3nomad" wrote:

> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/Sho...71057&SiteID=1
> I have a database on a server hosting multiple other databases and only this
> one had the issue. It's currently set to a limited growth of 200 mb with a 10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this problem
> and how to correct it.
> Thanks!
|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
>
> John
> "mp3nomad" wrote:
|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
[vbcol=seagreen]
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:

No comments:

Post a Comment