Viewing 6 posts - 31 through 36 (of 36 total)
I am not too familiar with SQL 6.5, so the following information only applies to SQL 7 and SQL 2000. It might work for SQL 6.5. I just don't have...
February 23, 2003 at 9:20 pm
shoayb,
I am glad you found this article helpful. In fact, you could easily edit that stored procedure and use it to trace deadlocks, do performence tuning and lots of other...
January 17, 2003 at 4:18 pm
Deema,
Thanks for reading my article.
It's normal for the file size to be 0 when the trace just got started. SQL Trace does not write to this file right away. For...
January 14, 2003 at 9:32 am
Hi,
There is one mistake in the beginning of the scripts. Instead of DROP PROCEDURE usp_Login_Audit_Trace, the article says DROP PROCEDURE dbo.spRoleMembers. My apologies and much thanks to reader William...
December 19, 2002 at 1:52 pm
Thanks again.
I incorrectly assumed that @p1...@pn are user-defined variables and that apprently caused some confusion. My apologies.
Brian is right. My earlier trace only traced the TSQL-SQL:StmtStarting. So the only results...
February 11, 2002 at 3:51 pm
Thanks guys.
I'm not interested in tracking the values of SQL server pre-defined variables, like @@ROWCOUNT or @@SPID (althrough it would be great to be able to track those as well)....
February 4, 2002 at 4:10 pm
Viewing 6 posts - 31 through 36 (of 36 total)