* This is the modus mailing list * Do you need the transaction logs on the tempDB? If not, why don't you restrict their growth for that database to a specific size to prevent them from filling your server.
Jim Barstow Sr. Network Engineer Diversified Solutions and Services, Inc. 22645 Canal Road, Suite B Orange Beach, AL 36561 251.980.8968 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lapo Nustrini Sent: Friday, January 16, 2004 10:24 AM To: [EMAIL PROTECTED] Subject: [Modus] MS SQL problem * This is the modus mailing list * Since a few days ago, the SQL server we use to store the quarantine has been playing up, and prevented Modusgate from archiving spam at an acceptable rate. The Modus Error logs show quite a few "timeout" errors such as: ---- MODUSADM log entry made at 01/16/2004 07:36:23 Mail Store error [0xE00E03E9]: State:S1T00,Native:0,Origin:[Microsoft][ODBC SQL Server Driver]Timeout expired On the SQL side, the major concern is the following entry in the SQL logs: "The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.." accompanied by: "Error: 9002, Severity: 17, State: 6" Reading the SQL documentation, I simply don't understand how this could be, given that the tempDB is recreated everytime SQL is restarted, and that there is about 5GB of diskspace for it to grow into. Has anyone seen this before? Vircom has been helping out on this one, but I thought I might run it past the mailing list just in case. Thanks, Lapo Nustrini Seanet Corporation 701 Fifth Ave, Suite 6801 Seattle 98104 WA (206) 343 7828 http://www.seanet.com ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line. ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line.
