• jasona.work (10/26/2016)


    Siberian Khatru (10/26/2016)


    So if I understand things correctly, if I have these set to Simple mode, then the size of the trans log is really not all that important since we will never be restoring it. So If I shrink these down to say 50MB (or whatever) they will only grow as large as they need to between backups to do minimal logging required for crash recovery and uncommitted transactions -- that kind of thing?

    Close.

    The size will still matter when you need to restore, because the restore process will create a log file the same size as it was when it was backed up (the size on disk, NOT the space used in the log file.) So if, somehow, one of your Simple recovery DB log files grew to 1TB, and you needed to restore a backup of that DB somewhere, you would need 1TB of space for the log file.

    Also bear in mind, unless you turn on the Auto-shrink option for your databases (please don't do that) your log file will never get smaller on its' own.

    Beyond that, yes, you've got the gist of it.

    'Zactly. And, it would take quite some time because the VLFs need to be formatted into the space created, much like reformatting a disk for DOS but slower.

    --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)