Re: SQL 2000 - Replication and LDF file



Des,
this will not aid in recoverability. You need both full database backups and
log backups to be able to restore to a point in time. So, best to use full
recovery mode and backup the database typically daily and the logs much more
frequently eg once per hour. Also, try to avoid shrinking of files.
Subsequent file growth is expensive in terms of processing power, and
shrinking of database files causes fragmentation.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)


.



Relevant Pages

  • Re: Trimming HUGE Transaction Log
    ... say backup the database, I really mean both. ... I added differential backups ... Most installations use fairly frequent log backups (depending ...
    (microsoft.public.sqlserver.tools)
  • Re: Database Size, Database Corruption, Message Store & Storage Group
    ... More careful monitoring of the server. ... Each extra storage group also requires more memory at startup, ... Also it is important to know if there was actually database corruption. ... In terms of backups, you should look at "how" you are performing backups. ...
    (microsoft.public.exchange.admin)
  • RE: Log Shipping and Full Backup Frequency. Advice?
    ... The transaction log is different; it is a recording of database actions. ... And, if you restore from any of these, you only get that state. ... This is not the case with the transaction log or its backups. ...
    (microsoft.public.sqlserver.server)
  • Re: Pervasive SQL 8.6
    ... and backups are done by copying the files off to tape - ... you'll want to have lots of memory on the server -- ... > drives for the database files. ... > some settings AWAY from what was normally considered optimal in order ...
    (comp.databases.btrieve)
  • Re: Pervasive SQL 8.6
    ... and backups are done by copying the files off to tape - ... you'll want to have lots of memory on the server -- ... drives for the database files. ... set up your SAN with a configuration of 80% memory set ...
    (comp.databases.btrieve)