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...

Just to add, you can enable the trace flags with the -1 switch/parameter without needing to restart SQL Server (which is not ideal in production environments), So, you can execute dbcc traceon (1204,1222,-1) which enables the trace flags for all (global) sql server sessions without the need to restart...