Sql-server – sql 2000 trace : sp_releaseschemalock profilersql-server-2000 For a SQL 2000 server, is it bad to see too many exec sp_releaseschemalock 1 events in a SQL trace file? Best Answer Since sp_releaseschemalock is an internal stored procedure, under normal circumstances, seeing many of it is not an issue. Related SolutionsSql-server – Sql 2000 attach Error 5172 The file's corrupt. You either need a backup, or you need to engage with a consultant who can try manually editing the file. (I'm not one of those consultants, and they're not cheap - you're in five-figure territory.) Sql-server – sql 2005 – trace capturing all events Just use a trace template. Click File, New Trace, and choose the Replay template. That'll get you everything that happens. Related QuestionSql-server – Running a sql server Trace of 1 GB using sqlcmdSql-server – How to upgrade a SQL 2000 Database to SQL 2005 – need confirmationSql-server – Where is this thestery trace going (SQL Server 2000)Sql-server – SQL Server 2000 trace file extensionSQL Server 2000 – How to Upgrade SQL Server EngineSQL Server Profiler – Comprehensive SQL Trace Events ListSql-server – Modern SQL Profiler against SQL 2000
Best Answer
Since sp_releaseschemalock is an internal stored procedure, under normal circumstances, seeing many of it is not an issue.