Re: [Emerald] I'm in Trouble

Patti Raatz ( (no email) )
Thu, 12 Aug 1999 09:41:39 -0500

>I would try specifying a new file name in the Tracing area of the ODBC
>Control Panel toy. After a reboot - or, at the very least, a quick toggle
>of the Start Tracing button - the new file should become locked and (I
>hope) the old one should be released.
I've checked all this out and also did as you suggested by creating
a new file. Toggled the Start Tracing button and rebooted and nothing has
chaged. The sql.log is now up to 1.5GB and counting.
I spent the night here (as I am sure many have done before me at
their own business) and I am getting really frustrated (can't imagine what
my customers are going through).

>Incidentally, unless this server is some kind of firewall/proxy or IP
>for your customers, this SQL blob shouldn't be impacting anyone's
>experiences with the outside world.
Then what would cause this problem for the majority (but not all) of
my customers. How can I find it and stop it? I guess I am too stupid for
this business but I am in so deep now that I can't back out (btw, I am a one
horse show in a very rural community).

For more information about this list (including removal) go to: