Last time I had out of control log growth, I had screwed up an update statement so that updating a single row was actually updating every row with the existing value. Did not change the data, but caused many transactions to be logged. Also look for a trigger that may be causing a similar problem. If you are not backing up the db or dumping the logs and have not set truncate on checkpoint, you will also have an issue as the logs will grow forever.
Justin -----Original Message----- From: Kelly Matthews [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 11:50 PM To: CF-Talk Subject: SQL Transaction Logs...? -- Spamex - Forums Now Available http://forums.spamex.com/forums/ -- Replies will be sent to [EMAIL PROTECTED] -- Additional Info: http://www.spamex.com/i/?v=52 Has anyone ever had a SQL 7 or 2000 database that wasn't that large. Have one that's about 9 megs. Where the transaction log was HUGE? My transaction log is 231 megs right now and rapidly growing. There is not that much update, insert, delete activity against the database so I am confused as to why this is happening. I run a ton of other databases where the transaction log is not so much larger then the database. Thoughts? Kelly ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
