I have a mere 100MB db with a 4GB transaction log. I want to truncate the log as I understand that truncating it will shrink the log by removing the transactions that have already taken place. However, the option to do a transaction backup is greyed out. I suspect this is from the db being in transactional replication with another server; however, I don't know for sure.
Are there any other ways that I can shrink the transaction log? I would like to do shrink it without taking the db offline either.
Are you using SQL 2000?
If so you can do that by the following
- Go to DB properties and change the backup type to FULL
- Take a backup of the database and keep it safe.
- Go to DB properties again change the backup type to SIMPLE
- Go to all tasks and Shrink the file
- Go to DB properties again and change the backup type to FULL again so that it logs everything.
Yes, I am using SQL2000. That's important information
SQL2000 on win2003.
smasanam: I tried that and it didn't shrink the log file. Still 4.5GB.
Is the log file important for transactional replication? This db is replicated nightly to another server. If everything is updated and fully bkup'd would the log file be necessary? Or could I just delete it?