Truncating the transaction log for a SQL Server 2000 database

Tags:
Microsoft SQL Server 2000
SQL Server database
SQL transaction logs
What is the best automated way to truncate the transaction log for a SQL Server 2000 database?

Answer Wiki

Thanks. We'll let you know when a new response is added.

If you do not need to keep the transaction log then simply change the recovery model from FULL to SIMPLE. The transaction log will automatically truncate every few minutes as the database checkpoints and flushes the transactions from memory to disk.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Brijesh
    Hi,

    Try this 

    BACKUP LOG databasename WITH TRUNCATE_ONLY
    DBCC SHRINKFILE (  databasename_Log, 1)
    or
    use master
    go
    dump transaction <YourDBName> with no_log
    go
    use <YourDBName>
    go
    DBCC SHRINKFILE (<YourDBNameLogFileName>, shrinking size) -- 
    go
    -- then you can call to check that all went fine
    dbcc checkdb(<YourDBName>)
    


    9,870 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following