One of my DBs is about 10 GB, the autogrowth creates performance problems.
I manually increase the size as needed. Any suggestions of a better solutio
n to this. May be a job that increases the size at a specific time?
ThanksNiles,
you could simply make the database file size extremely large in one alter
database statement and do this out of hours.
Autogrowth is a double edged sword as it makes maintenance easier but the
DBA loses control of when such increases occur, potentially resulting in
them happening during peak hours. The same would apply to an alert.
You could also schedule a job to run out of hours which examines the results
of sp_spaceused and then determines if an increase in size is required.
HTH,
Paul Ibison|||Yes I agree with Paul. Why not make the DB size something large enough so
you don't have to worry about it for a year or more? If you know it will
get to 20GB in a year then make it that large now. There is no penalty for
too much free space but there is a big one for too little.
Andrew J. Kelly SQL MVP
"Niles" <anonymous@.discussions.microsoft.com> wrote in message
news:7435AFFE-47B9-4520-945E-9ED198C6B258@.microsoft.com...
> One of my DBs is about 10 GB, the autogrowth creates performance problems.
I manually increase the size as needed. Any suggestions of a better
solution to this. May be a job that increases the size at a specific time?
> Thankssql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment