Did you truncate the transaction logs after making the switch to simple? John
________________________________ From: [EMAIL PROTECTED] on behalf of Lapo Nustrini Sent: Fri 1/16/2004 5:24 PM To: [EMAIL PROTECTED] Subject: [Modus] MS SQL problem * This is the modus mailing list * Unfortunately, we already did this. It seemed to resolve the problem (yesterday) but started failing again after a few hours. Also, even after shrinking the tempdb (as suggested by a previous poster), the problem continues to reoccur with "The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.." errors showing up in the SQL log every 10 - 15 minutes. Thanks, Lapo On Jan 16, 2004, at 1:24 PM, Greg Miller wrote: > * This is the modus mailing list * > > If you are running SQL Server Version 2000 change the database recovery > option from "Full" to "Simple" under the database properties page. > > -----Original Message----- > From: Lapo Nustrini [mailto:[EMAIL PROTECTED] > Sent: Friday, January 16, 2004 4:23 PM > To: [EMAIL PROTECTED] > Subject: [Modus] MS SQL problem > > > * This is the modus mailing list * > > Hello Suneel, > the properties sheet for my modusDB does not have an option to > "Truncate Log". > Maybe I'm missing something and looking in the wrong place... > > The strange thing is that the tempDB is _never_ out of disk space. It > just says it is. > Each time I restart the sql service, it gets recreated with a different > size, but the error still comes up regularly, even as the DB grows. > > I've now just shrunk the tempdb to 1mb and waiting to see what happens. > > Thanks for any other suggestions, > > Lapo > > > On Jan 16, 2004, at 11:30 AM, Suneel Jhangiani wrote: > >> * This is the modus mailing list * >> >> Go into Enterprise Manager and find your Quarantine Database, right >> click on it select properties and ensure that the Truncate Log setting >> is checked. This should help remove the burden on the TempDB. >> >> --- >> Never have I seen a word as accurate as politics. Poly meaning many, >> and >> tic being a blood-sucking thing. >> >> >> (--------------------------------) {(((((( >> ( Suneel Jhangiani ) /_ _ ) >> ( Technical Director ) ( . . ) >> ( Inter-Computer Technology Ltd. ) ( / ) >> (----------------------------------oOOo------------oOOo----) >> ( 40 James Street Tel: +44 (0) 20 7486 9601 ) >> ( London W1U 1EU Fax: +44 (0) 7050 678 978 ) >> ( United Kingdom Email: [EMAIL PROTECTED] ) >> ( Website: http://www.inctech.com ) >> (----------------------------------------------------------) >> >> >> >> >> -----Original Message----- >> From: Lapo Nustrini [mailto:[EMAIL PROTECTED] >> Sent: 16 January 2004 16:24 >> 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. >> > > > ** > 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. > ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line.
<<winmail.dat>>
