• matt6749 (7/30/2014)


    Well, after a crash course in log files, thanks to everyone here, here's what I believe I have to do:

    My hosting company limits my combined db + log size to 400mb.

    Db is in Simple recovery mode.

    The log still grew to over 400mb with the last run of my transactions. Using explicit transactions (BEGIN TRANS..COMMIT) did not help this.

    So I've concluded that I HAVE to shrink the log (unfortunately) after I run these transactions (weekly).

    After shrinking I will rebuild the indexes to help reduce the fragmentation.

    I can't see any other way to handle this.

    Sigh...

    Is there any way you can decrease the size of your transactions? That's pretty restrictive sizing from the hosting company.

    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