Re: archive logging the log file
From: Dan Guzman (guzmanda_at_nospam-online.sbcglobal.net)
Date: 12/03/04
- Next message: Steve Kass: "Re: Numeric format - International settings"
- Previous message: David Gugick: "Re: SET NOCOUNT ON - am I doing this wrong?"
- In reply to: learningdba: "archive logging the log file"
- Next in thread: Wayne Snyder: "Re: archive logging the log file"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Dec 2004 23:00:47 -0600
I believe you are referring to transaction logs. The proper way to manage
transaction logs for databases in the FULL or BULK_LOGGED recovery model is
to backup the transaction log periodically. This will remove committed data
from the log (keeping the size reasonable) and allow you to use the log
backups in conjunction with database backups as part of your recovery plan.
A common practice is to backup to disk and then archive those backups to
tape. You can setup database maintenance plans to perform both database and
transaction log backups or create and schedule your own backup scripts. See
the Books Online for more information.
-- Hope this helps. Dan Guzman SQL Server MVP "learningdba" <learningdba@discussions.microsoft.com> wrote in message news:6BAE1103-01FC-45A4-B57E-B8FCD9AA86E3@microsoft.com... >I am new to SQL Server, but I cannot seem to find any way that SQL Server > will automatically move a log file (when it isn't needed anymore) off to > archive. Is the only way I can do this by setting up a batch process and > doing it myself? > > Help?
- Next message: Steve Kass: "Re: Numeric format - International settings"
- Previous message: David Gugick: "Re: SET NOCOUNT ON - am I doing this wrong?"
- In reply to: learningdba: "archive logging the log file"
- Next in thread: Wayne Snyder: "Re: archive logging the log file"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|