Shrink your SQL 2005 transaction logfiles
This might come in handy for some of you, as it did for me. I normally don’t have problems with large transaction logfiles, but on our acceptance machine we have mirrored the production database. As it’s replicated, the databases are installed multiple times on the machine. In theory it’d be best to have them on multiple machines (to mirror production exactly), but we chose multiple SQL Server 2005 instances.
When the transaction logfiles are growing they take up a huge amount of diskspace. So in our script to restore the environment, we’ve included a few T-SQL statements to set the recovery model to simple and shrink the transaction logfiles immediately. Here’s the code, it might come in handy when you’ve got a database on your own machine as well.
ALTER DATABASE [YourDatabase] SET RECOVERY SIMPLE WITH NO_WAIT
DBCC SHRINKFILE (YourDatabase_log, 10)
You don’t want to set the recovery model to simple on critical databases! If you’re not sure, just don’t change the recovery model. Transactional replication uses the transaction log and if the service agent stops, all transactions are stored in the log to be synced later.