Re: SQL.LOG

Dale E. Reed Jr. ( (no email) )
Fri, 16 Jan 1998 14:46:42 -0800

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Previous message: David Moore: "Its back again (SQL error 2627)"
Next message: Dale E. Reed Jr.: "(no subject)"
Maybe in reply to: Victor: "SQL.LOG"
Next in thread: Danny Sinang: "Re: SQL.LOG"

Victor wrote:
>
> Dale,
>
> I found what is causing the server to work so hard, the information is
> being recorded in the SQL.LOG file and I can't find where to stop it. Other
> times I just had to go to Control Panels ODBC32 and select the tracing tab
> and click on stop tracing....... but this time that tab has the "Don't
> trace" option selected, is there any other place in SQL- EM where one sets
> than up.

Thats the typical place. Do a start then a stop and see if it stops
it.

> Also, do I need to have SQLExecutive running as a service? can that be the
> cause of the problem? I gotta stop this thing, the SQL.LOG is growing at
> fantastic speeds!!

I doubt its SQL Executive.

-- Dale E. Reed Jr.  (daler@iea.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |   http://www.iea-software.com

Previous message: David Moore: "Its back again (SQL error 2627)"
Next message: Dale E. Reed Jr.: "(no subject)"
Maybe in reply to: Victor: "SQL.LOG"
Next in thread: Danny Sinang: "Re: SQL.LOG"