newbie backup question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Josephine (anonymous_at_discussions.microsoft.com)
Date: 06/30/04 

Date: Wed, 30 Jun 2004 07:26:24 -0700

Please help clear up my confusion...
I have a database that was set in FULL recovery mode and
the transaction log was not being backed up. To stop the
log from growing, I switched it to SIMPLE, but after last
night's backup I still have a 12 GB log file.
How do I get the transactions to commit to the .mdf file?
My concern is the data is just there in the log and if I
back it up it isn't commited to the .mdf file.
Backup the log file and then continue with the simple
recovery backups?
Is there a way to do this in EM?
If I do this do I want no_truncate, truncate on chk pt?
Thanks in advance for help,
Josie.

Relevant Pages

  • Re: Still dont understand log backups
    ... The transaction log, whether or not it is one or many files, is a serial, ... until the end of the physical log file is reached. ... backup is executed, the active "virtual" logs are backed up, but the ... Using BULK LOGGED, does the online log file contain EVERY transaction for all time -- given that I don't truncate it manually? ...
    (microsoft.public.sqlserver.server)
  • Re: Log Shipping: question about secondary dB mode?
    ... Regular transaction log backups will allow the committed and backed up portion of the log file to be reused for new transactions. ... And last to recover the db you restore the last log file using the WITH RECOVERY option and you should be all set. ... all the backup and restore jobs are proceeding without errors. ...
    (microsoft.public.sqlserver.tools)
  • Re: SQL 2005 Shrink issue
    ... When you perform a Transaction Log Backup, passive virtual logs in your transaction log file are deleted. ... you can change your database's recovery model to SIMPLE when you want to get rid of your passive virtual logs in your transaction log file. ...
    (microsoft.public.sqlserver.tools)
  • Re: Restore Database w/Large Transaction Log File
    ... If I am reading you correctly, the backup has already been trasmitted to the ... AGAIN, just like the other respondents have told you: shrink the log file, ... Shrinking a database transaction log file that has that has been pre-gone to 200 GB in size, will not save any disk space on the restore. ...
    (microsoft.public.sqlserver.server)
  • Re: SQL 2005 Shrink issue
    ... We just used MS SQL 2005 Mngment tool and did a FULL BACKUP on the DB...then ... FULL BACKUP then a TRANSACTION LOG backup. ... all of your active transactions). ... In FULL recovery mode, this is not a wise backup model. ...
    (microsoft.public.sqlserver.tools)