Hi, Regarding to this transaction log full issue, it is not how you truncate the transaction log file but how the transaction log file got full that interests me. We have a v7 ARS server with IM, PM, CM, SLM, CMDB, EIE for SQL installed. After about 6 months running, we hit the same situation. There are about 20000 incident tickets in the db and 2000 contact information replicated/updated nightly. It end up with a more than 100GB transaction log file. Does anyone know what kind of behavior would generate a log file so large? Thank you.
DJHuang 2007/7/12, Broyles Robert K Mr CTR USAF 96 CS/SCCE <[EMAIL PROTECTED]
: Thanks Joe. I went back and reread the SQL books online and say that my syntax was wrong. I didn't need to specify TRUNCATEONLY if I pass it a file size. Rob _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
