Hi!
I use proc handling special business logic (I also use constraints, indexes for that ;-)
Now I have a situation where I should check multiple rows with an proc.
Preventing multi-user issues I want to lock the table (yes, yes potential performance issue, but in this case there are few simultaneous jobs) - in Oracle I could lock the table, but what to do in SQL Server?
Maybe you have an better alternative, then let me hear ;-)
Or should I use "begin transaction"...
Thanks for help
Hmm, maybe
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
-- DO YOUR stuff
SET TRANSACTION ISOLATION LEVEL READ COMMITTED
will be the solution...
Some comments?
sql
No comments:
Post a Comment