If you don't have a good SQL maintenance plan in place, the transaction log just grows and grows and grows over time. The transaction log can grow quite a bit if you run, say, an escalation or filter that modifies 1000s of records. Then do that a few days a week, and in no time the transaction log is huge.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of DJHuang Sent: Thursday, July 12, 2007 9:49 AM To: [email protected] Subject: Re: Transaction log is full. ** 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] <mailto:[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" __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
