Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
magictech
Starting Member
44 Posts |
 Posted - 2004-11-09 : 11:32:57
|
| Every time I'm running a job on one of the databases my SQL Server 2000 machines and at the same time click on the current activity node, I get an error message that says "Error 1222:Lock request time out period exceeded". I'm having problem understanding this error message since the reason I click on the current activity node is just to see what other process is running on this server, which shouldn’t affect any particular object. Has anyone had this problem? If so, how did they fix it? Thanks in advance |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-11-09 : 18:13:43
|
| I had this problem on SQL Server 7.0 when my users were running large reports. It would just lock up on me then eventually timeout. To view current activity, just use sp_who or sp_who2 in Query Analyzer. Enterprise Manager should be used at a minimum.Tara |
 |
|
|
magictech
Starting Member
44 Posts |
Posted - 2004-11-11 : 10:52:22
|
| Tara thanks for your respond. My question is can this problem be fix, since it preventing other users from using other databases on the server that's having this problem? Why should a lock situation affect other databases and or application that are running on the same server? Any information will be greatly appreciated.Regards |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-11-11 : 12:30:37
|
| Because locks use up resources on the server. I would run SQL Profiler to determine what is going on. And don't view Current Activity from EM, it just slows things down even more.Tara |
|
|
|
|
|
|
Error 1222:Lock request time out period exceeded