Assigning a new log file to the DB

  • Hi everyone,

    If I was to ensure that my database will not perform any transactions, would it be possible to somehow get rid of the old log file and assign a new log file to the database to work with? Of course, I am assuming that if there are no transactions for say 10 minutes, then all previous transactinos have been commited. Any help would be greatly appreciated. Tx.

  • Can you get down time of 10 minutes?

    You can down the database, detach, attach without the logs, create new logs....

    Joseph

  • Thanks for the help Joseph.

    Yes, I can get that much down time. I am not able to back up the logs of this database...getting some errors when I try to. So it is top priority to fix the issue. A new log file will assign a new log sequence number, which hopefully will fix the log backup problems. JFYI, here is the error I get when I try to back up the logs:

    The media family on device '\\.\pipe\BackupExecSqlAgent-{ba407e03-4b1e-47d3-884a-4d24a7f36b37}-00' is incorrectly formed. SQL Server cannot process this media family.

    Database or database element is corrupt

  • Also, is there a way to tell SQL 2K to commit all transactions in a database? Just want to make sure that all transactions are commited to disk before I detach/attach. Tx.

  • Doesn't issuing the Checkpoint command do this?

  • Yes, that's it Linda. Thank you!

Viewing 6 posts - 1 through 5 (of 5 total)

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