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 |
|
GhantaBro
Posting Yak Master
215 Posts |
 Posted - 2008-11-18 : 11:26:44
|
| Hey guys,I have an SP where one part updates a Control Table and does the extract... The SP is created in such a way that it can be run concurrently more than once; however, for the SAME record in control table, if the SP runs concurrently then one run will update the control table and the next run will use that updated control table value.... what should I do to fix this?? I hope I am making sense on trying to explain the issue... should I lock the CONTROL Table? Or is there anyway I lock a particular row only (say if two run is using the same record in the Control table)... What should be the best way to fix this problem. Thanks guys for your time and help.. |
|
|
GhantaBro
Posting Yak Master
215 Posts |
Posted - 2008-11-18 : 11:51:37
|
| bumping this up.. |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-11-18 : 12:34:45
|
| Read about ISOLATION LEVELs in books online. |
|
|
|
GhantaBro
Posting Yak Master
215 Posts |
Posted - 2008-11-18 : 14:35:43
|
| thanks visakh! |
|
|
|
|
|
|
Concurrent Run Table Lock