Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

db autogrowth settings Expand / Collapse
Author
Message
Posted Tuesday, January 10, 2012 6:45 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 12:02 PM
Points: 46, Visits: 519
So in effect then data and log files are not growing because they have so much free space and the 3% growht is not revelant at the time.
Post #1233147
Posted Tuesday, January 10, 2012 6:47 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Thursday, November 20, 2014 8:50 PM
Points: 20,584, Visits: 9,623
Tim Jacobs-356724 (1/10/2012)
So in effect then data and log files are not growing because they have so much free space and the 3% growht is not revelant at the time.


Yes.


Why do you want them to grow so bad??
Post #1233153
Posted Tuesday, January 10, 2012 7:03 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 12:02 PM
Points: 46, Visits: 519
Ninja, I don't want them to grow bad just trying to understand if the 3% is even revelant at this time given the free space. Some literature suggest never using autogrowth but monitor and adjust accordingly. I do appreciate the guidance from you and John.
Post #1233175
Posted Tuesday, January 10, 2012 7:08 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Thursday, November 20, 2014 8:50 PM
Points: 20,584, Visits: 9,623
Tim Jacobs-356724 (1/10/2012)
Ninja, I don't want them to grow bad just trying to understand if the 3% is even revelant at this time given the free space. Some literature suggest never using autogrowth but monitor and adjust accordingly. I do appreciate the guidance from you and John.


Never RELY on autogrow. It's an insurrance against unforseen data spikes or other problems.

You should set it to 500 to 2000 mb and move on to your next task. That way the db(s) won't break (running out of space does that, no more transactions can happen, but read is ok).
Post #1233181
Posted Tuesday, January 10, 2012 7:21 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 12:02 PM
Points: 46, Visits: 519
Thanks Ninja. So as you and John suggested the final settings on SQL 2000
autogrowth=Yes
In Megabytes 500-2000
Unrestricted file growth = Yes

monitor using sp_spaceused or via scipt and keep doing what we're doing with the backups.

Post #1233198
Posted Tuesday, January 10, 2012 7:23 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Thursday, November 20, 2014 8:50 PM
Points: 20,584, Visits: 9,623
Yes.
Post #1233200
Posted Tuesday, January 10, 2012 7:25 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 8:21 AM
Points: 5,437, Visits: 10,128
Unrestricted file growth will depend on whether your database shares the disk with other databases that may also want to grow. If it does, then it's wise to set a maximum growth for each file on the disk in case one of them suddenly grows and tries to consume the whole disk.

John
Post #1233206
Posted Tuesday, January 10, 2012 8:30 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 12:02 PM
Points: 46, Visits: 519
Thanks John that's an interesting point. The disk is shared with a read only copy of our production db(the one we've been discussing) that gets restored every early morning from the current backup. The disk is 350G with 73G used.
Post #1233280
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse