March 24, 2011 at 10:22 am
Trigger is causing a lock in a system.
I have a table which have trigger to call stored procedure, that stored procedure have 2 updates and calls another procedure and sometimes causing to slow down the table.
How can I find out what exactly in that stored procedure is slowing down.
Thank you
March 25, 2011 at 1:30 am
Check the execution plan of the stored procedure
March 25, 2011 at 1:59 am
Profiler/server-side trace. Statement completed event.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 25, 2011 at 7:13 am
I just added,but how to add database name,so I would know for which database and is it possibile just to run in for one database?
Thank you
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply