The place where I work has very recently adopted a new computer system that utilizes SQL Server 2005. The most significant problem so far has been assisting users who cannot access data because it is locked by another user. Is there any way to identify the specific user who is locking a record? I have no experience with SQL Server at all, so I'm not sure if this qualifies as a stupid question, an easy question, or both. Any assistance would be greatly appreciated and would also help me to not be run out of town by a horde of angry users.
The following links should give you much of information. SQL Server Performance - what it takes for a newbie DBA in resolving performance issues? Is ASP.NET invovled - if so refr to SQL Server 2005 - concurrency & locking with ASP.NET applications TSQL to findout blocking and locks on a SQL Server? Identify and troubleshoot slow running queries in SQL Server SQL Server Cursors usage and performance - cursed SQL Server 2005: Slow running queries - Blocking and Index problems Performance - check whether it is affecting application or system, don't blame SQL Server alone