• Satish Nagaraja (9/16/2014)


    Hi All,

    I was having interesting discussion on estimation of log file with a fellow collegue who happens to be quite knowledgable as well.

    He told me if we identify the most frequently hit tables for a database and then (sum their sizes * 1.5) for OLAP we get rough estimate for disk space to be allocated for log file.

    Are there any other options ? Can you share some links which I can read about ?

    Cheers

    Sat

    On a new database, you normally have no idea how big tables will get so it would simply be an order of magnitude guess while observing best practices to control the number of VLFs spawned during growth.

    For existing systems, the current size of the log file plus some room for near term growth is a pretty good guess. 😀

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)