1MB datafile growth size?

  • I'm aware of the issues with sizing your logfile growth size too low (causing too many VLFs, etc). But I haven't seen much about the datafile side of it.

    Are there any benchmarks specifically on setting datafile growth so low (on databases 1-100Gb in size)? Are there circumstances in well utilized servers where that might be warranted?

  • It is of course possible on almost static databases with mostly reads and hardly any inserts/updates, but in general it is unlikely. There may be other reasons where one would like to control the growth but a low auto-growth size setting is not the right method for that either.

    😎

  • I'd never leave a database file autogrowth setting at 1MB. The smaller the growth size the more physical fragmentation the file will have on disk. The next physical block on disk might not be available when the autogrow happens. You should manage growth manually and the autogrow should be an emergency only operation when something outside the bounds of normal activity happens or load changes suddenly. You can monitor file usage to determine the growth pattern of the data so you can manually grow database files during a maintenance or low use period and allocate enough space for 6 months to a year.

  • I wouldn't leave filegrowth set at 1mb. There isn't much use for a growth that low. With Instant file initialization, data file growths in the GB range are near instantaneous.

    And then of course there are the problems that Jack raised.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

Viewing 4 posts - 1 through 3 (of 3 total)

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