Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
venkath
Posting Yak Master
202 Posts |
 Posted - 2008-09-15 : 13:34:15
|
| Hi allTransactional log file of a database has grown to 60GB though the database is in SIMPLE recovery mode.The database is being used as a subscriber in transactional replication.Could you please let me know what are the scenarios that cause the transactional file to grow that huge despite the db in simple recovery mode.Thanks in advance. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-09-15 : 13:37:25
|
| Replication definitely uses the transaction log, although I thought it was on the publisher side probably depends on whether it is push or pull. Database mirroring also uses the transaction log.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
venkath
Posting Yak Master
202 Posts |
Posted - 2008-09-15 : 13:42:39
|
| This is Push subscription.Not using Database mirroring. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-15 : 15:03:00
|
| You can truncate log if in simple recovery model. |
|
|
|
Yeoh Ray Mond
Starting Member
49 Posts |
Posted - 2008-09-16 : 11:23:28
|
| Perhaps you have an old transaction that is still active, that is preventing the log from being truncated? You can run DBCC OPENTRAN on that database to check if this is the case.Another possibility is that you had a large transaction that generated that many entries in the transaction log. A database running in SIMPLE recovery does not keep committed transactions around, but if a transaction made a large number of changes, the transaction log will still need to accommodate the changes made by the transaction.Ray Mondhttp://www.sqlbackuprestore.com - your quick guide to SQL Server backup and recovery issueshttp://www.sqlinspect.com - in-depth query analysis for SQL Serverhttp://www.sqlimageviewer.com - retrieve, view, convert and export images directly from SQL Server, SQLite and Firebird databases |
|
|
|
|
|
|
Log file size grown up 60GB in simple recovery