database in recovery model simple, error transaction log

  • sorry for the late response.

    here:

    http://support.microsoft.com/kb/873235

  • Sorry, but I don't see anywhere where they say to limit the max size.

    Under the section "Prevent the transaction log files from growing unexpectedly" there's

    Set the current size to a large value

    Set the auto grow to fixed amounts not %

    Change recovery model

    Design transactions to be small

    Back the log up frequently

    Ensure that transactions can't be left uncommitted

    Use index defrag rather than reindex

    Am I not seeing a paragraph somewhere?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • to Set the current size to a large value is a limit.

    to Set the auto grow to fixed amounts not % is a limit

  • fred2002 (10/27/2009)


    to Set the current size to a large value is a limit.

    To set the current size to a large size is to just set the current file size. Nothing about the maximum limit on the file size.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 4 posts - 16 through 18 (of 18 total)

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