Could the EIE memory leak be contributing to your oversized transaction log issue?
Just thought I'd give you something to look in to. I think the EIE memory leak still exists to some extent in Patch 4 and 5. --- DJHuang <[EMAIL PROTECTED]> wrote: > Carter, > > I do agree with you that there should be a regular > database maintenance > plan in place. > As the system keep updating and customizing, DBA > didn't put our ARS DB > into the regular maintenance process. > But now the DB issue has been taken care of. > Thanks. > > DJHuang > > 2007/7/12, Carter, Craig J Civ ARPC/DPD > <[EMAIL PROTECTED]>: > > > > ** > > > > A transaction log is a log of transactions¡Xit > will continue to grow over > > time until it is backup up/truncated. > > > > > > > > You need to set up a database maintenance plan to > regularly backup your > > database (includes the log file). Otherwise, it > will continue to grow over > > time until you run out of disk space. It's > surprising to hear people are > > not performing regular SQL backups. We have > hourly transaction log backups > > that run during core work hours along with full > database backups daily. > > We've used these several times to recover data > that was accidentally > > deleted, etc. > > > > > > > > There is an option to remove free space when > defining the maintenance > > plan. When doing a complete backup under normal > conditions, you shouldn't > > need the extra truncate command. It is handy when > running large data > > imports, etc. > > > > > > > > CRAIG CARTER > > > > Remedy Skilled Professional > > > > > > > > > > > > *From:* Action Request System discussion > list(ARSList) [mailto: > > [EMAIL PROTECTED] *On Behalf Of *DJHuang > > *Sent:* Thursday, July 12, 2007 8: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] > > >: > > > > 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___ > > __20060125_______________________This posting was > submitted with HTML in > > it___ > > > ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
