we've had on one particular database since SQL7 on NT4.
The database in question is set to autogrow by 10% (currently sitting
at 31Gb total size). However, last week users complained of a
slowdown in performance. When we checked we found that only 14Mb was
free on the database (we thought it would've grown automatically
before then), and when we added an additional 1Gb manually performance
picked up.
Does SQLServer wait until all the space is used up (i.e. 0% free)
before autogrowing? Even at that, we've never actually had the
database grow automatically - we've always had to add space manually.
Settings on this database, and one that does grow automatically,
appear to be the same (have also checked via sp_helpdb). So where
does the problem lie?
Any help you can give would be greatly appreciated.Do you have large transactions occurring in that database? If so, this KB
article might apply to your case:
http://support.microsoft.com/defaul...kb;en-us;305635
Simon
"LizP" <liz.porteous@.scottishfriendly.co.uk> wrote in message
news:8170ed5a.0306240753.1dd021f8@.posting.google.c om...
> We're using SQL2000 on Windows 2000 Server, but this is a problem
> we've had on one particular database since SQL7 on NT4.
> The database in question is set to autogrow by 10% (currently sitting
> at 31Gb total size). However, last week users complained of a
> slowdown in performance. When we checked we found that only 14Mb was
> free on the database (we thought it would've grown automatically
> before then), and when we added an additional 1Gb manually performance
> picked up.
> Does SQLServer wait until all the space is used up (i.e. 0% free)
> before autogrowing? Even at that, we've never actually had the
> database grow automatically - we've always had to add space manually.
> Settings on this database, and one that does grow automatically,
> appear to be the same (have also checked via sp_helpdb). So where
> does the problem lie?
> Any help you can give would be greatly appreciated.
No comments:
Post a Comment