June 1, 2009 at 3:34 am
On SQL Server 2000 it was so simple to monitor blocking and locks on the database through management current activity, why change simple things and make things so complicated or is their an easier way I just don't know of.
I understand you can query the db dm_tran_locks but this shows all the locks on the db. Is their an easier way to see what/who is causing the block and who/what is blocking the db
June 1, 2009 at 5:44 am
Well you can see the same on 2008 as well, Activity Monitor, this has got many more features than 2000 🙂
June 1, 2009 at 6:14 am
I'd tried using the activity monitor, under the processes tab it shows what is currently running. I cant see much their How can I extend those columns because I can't seem to strech the column
September 12, 2009 at 6:52 am
Hi
check weather this link will help you
http://www.eweek.com/c/a/Database/How-to-Monitor-and-Protect-Your-Databases/?kc=rss
September 12, 2009 at 11:43 pm
Activity Monitor has taken a major step backward in 2008.
Sadly it is so far unchanged in R2 🙁
Adam Machanic has written some awesome code, which I strongly encourage you to try out:
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
September 30, 2009 at 4:06 pm
what about "sp_who2 Active" or the blocked process report?
October 30, 2009 at 2:28 pm
Hi,
The best way you can do is Try SQL Server Profiler, that is very useful to check database lock/trace or whatever you like to see the transactions.
Also when you create the Template, you can filter by login user, by description, etc..
I had some problems with Deadlock in my application and I have resolved so quickly using Profiler to identify where the problem is causing the lock.
I hope it helps.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply