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 |
|
rubs_65
Posting Yak Master
144 Posts |
 Posted - 2004-01-12 : 15:11:07
|
| Hi,We are having blocking problem when 1 process is reading data from table1 and other process try to update rows in table1. It was working fine earlier but somehow for last few days we see that select statement is holding SHARED lock on table1 whereas we expect it to take IS lock on table and S lock on desired rows. Due to S lock on table second process is not able to get IX and blocked. we are thinking it might be related to MEMORY issue and 1st process is escalation S locks on rows to table SHARED LOCK. so we are thinking of using ROWLOCK during select statement.ANY opinion on our finding and other alternative strategy is appreciated.Thanks--rubs |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-12 : 15:41:06
|
| I would not recommend using ROWLOCK. If blocking is suddenly a problem, you need to take a look at the performance of the server. You might now have a hardware bottleneck. If you do, it can be found using Performance Monitor.Tara |
 |
|
|
denisemc
Starting Member
26 Posts |
Posted - 2004-01-12 : 18:42:02
|
| How many rows total in the table in question? How many rows are returned by the SELECT? |
|
|
|
|
|
|
Locking escalation problem