What is the SQL command for emptying these? Is there one? Google hasn't been any help.

The log for the site I'm working with fills up continually, truncation only works to a point and I'm tired of calling them up to empty the transaction log for me. Any websites are greatly appreciated.

5/23/2006 10:03:37 AM

http://www.databasejournal.com/img/1569051ex01.txt

see if that helps.

Also, maybe BACKUP LOG [database name] WITH TRUNCATE_ONLY

5/23/2006 3:04:00 PM

yeah I tried the backup log with Truncate_only and it didn't work. My situation ist that I can throw SQL commands at the database but that's it. I don't have admin access and the support is well... stubborn.

I was hoping their might be a command like "BACKUP LOG [database name] WRITEOVER"... or such. Something that would let the first entry in the log be overwritten by the last once it reaches it's max size limit.

Side Note: No i can't turn it off.

[Edited on May 23, 2006 at 3:45 PM. Reason : !]

5/23/2006 3:45:29 PM

I'm guessing you've already seen this link?

http://msdn.microsoft.com/library/en-us/architec/8_ar_da2_7vaf.asp?frame=true

5/23/2006 10:25:49 PM

damn! that was what i was looking for. Unfortunately the command didn't work. I don't have the permissions to turn in off. I found out later was that this was the primary means of restoring a database they have. They do night backups as well but perfer to use the log to restore. Sigh...

I've never had this occur before since I've been spoiled and always had the equipment locally. I've never once run into this transaction log problem though. I guess it's the limit in size they have. My options for it on my servers were "Keep all records for 90 days". which translates to "I don't give a fuck how big it is, just keep all records for 90 days".

5/23/2006 10:54:32 PM

^ hehe sorry about my english there. I was hella tired.

5/24/2006 8:44:34 AM