Hi,
The last weeks MSSQL 2000 profiler includes dozen of events referring to SQL_TRACES, events that don't want to have and make the profiler unsable for me, since they create continously dozen of unused traces, like:

exec sp_executesql N'SELECT CREATED_BY, DEFAULT_LOAD_INTERVAL_IN_SECONDS, ID, LOAD_DATA_TRACE_PATH, NAME, PASSWORD, SERVER_NAME, SQL_VERSION_ID, TRACE_PATH, USERNAME, USE_WINDOWS_AUTHENTICATION FROM SQL_SERVERS WHERE (ID = @ID)', N'@ID uniqueidentifier', @ID = 'E31F6128-FC11-4931-87DD-77CAA107E2E0'


exec sp_executesql N'UPDATE SQL_TRACES
SET TRACE_SQL_SERVER_ID = @TRACE_SQL_SERVER_ID, SQL_TRACE_ID = @SQL_TRACE_ID, TRACE_DATA_PATH = @TRACE_DATA_PATH,
START_SCRIPT = @START_SCRIPT, STOP_SCRIPT = @STOP_SCRIPT, PROFILER_EVENT_ID = @PROFILER_EVENT_ID
WHERE (ID = @Original_ID);
SELECT ID, TRACE_SQL_SERVER_ID, SQL_TRACE_ID, TRACE_DATA_PATH, START_SCRIPT, STOP_SCRIPT, PROFILER_EVENT_ID FROM SQL_TRACES WHERE (ID = @ID)', N'@TRACE_SQL_SERVER_ID uniqueidentifier,@SQL_TRACE_ID int,@TRACE_DATA_PATH varchar(250),@START_SCRIPT text,@STOP_SCRIPT text,@PROFILER_EVENT_ID uniqueidentifier,@Original_ID uniqueidentifier,@ID uniqueidentifier', @TRACE_SQL_SERVER_ID = '45DEA2DB-A04C-4438-AFDB-0FEC1E38D3DD', @SQL_TRACE_ID = 2, @TRACE_DATA_PATH = 'C:\Temp\885e6ab4-28c9-4801-86eb-6947eeabedc720100314083533796.trc', @START_SCRIPT = 'declare @rc int;', @STOP_SCRIPT = 'sp_trace_setstat', @PROFILER_EVENT_ID = '59B19BD0-2938-4346-93EC-420059A8CE2C', @Original_ID = '885E6AB4-28C9-4801-86EB-6947EEABEDC7', @ID = '885E6AB4-28C9-4801-86EB-6947EEABEDC7'


SELECT ACTIVE, AUTOMATICALLY_DELETE_TRACE_FILES, CREATED_BY, DATE_CREATED, ID, INCLUDE_NULL_DATABASE_NAME, IS_SERVER_LEVEL_TRACE, LAST_LOADED_DATA, LAST_RUN, LOAD_INTERVAL, LOAD_TRACE_FILES_DIRECTLY_TO_PROFILER_DB, MAX_FILE_COUNT, MAX_FILE_SIZE, NAME, STARTED_FROM_SCHEDULE, STATUS, TOTAL_ROWS FROM TRACES WHERE (STATUS = 1) OR (STATUS = 3)



Do you know how to get rid of these traces???

Amy \be it ahs to do with the installation of MSSQL 2005 as well??

Best Regards,
Manolis Perrakis