Post reply

transaction log keeps growing

  • July 20, 2004 at 10:33 am

    #84980

    This problem is only on several databases on the server! is there another way?

    is this the only choice when the transaction log keeps growing and you can not do frequent backups due to multiple databases. -  After changing the simple recovery mode, however, you'll need to clear the logs the first time with (a) dump tran dbname with truncate_only, (b) and from within the database -- DBCC SHRINKFILE (log_file_name)

    and if so is there a way around - "You can set the database to Simple Recovery Model.  This will cause SQL Server to clear completed transactions from the log regularly.  One note of caution: you lose point in time recoverability by doing this.  It is NOT recommended for a production transactional database." some of the databases may be jproduction databases.

    Is there another way to autoshrink a transaction log on only one or two databases on a server that has multiple databses that you do not want to clear often. but also do not want to lose the point in time recoverability on those one or two databases?

  • July 20, 2004 at 10:39 am

    #515311

    Thanks for this. Along those lines, database backups don't truncate or clear the log, so you need to be sure you add those in as well if you are not in simple mode.

Viewing 2 posts - 1 through 1 (of 1 total)

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