Isolation Levels
-
I have seen lot of embedded sqls being used in front end coding on client side. Also before these sqls are called isloation levels are explicitly set up based on the requrements. Is it a good idea to set these isolation levels or is it advisable to use the default level. Any thoughts/feedback on this will be greatly appreciated.
TIA
-
In most cases the default is just fine. It really depends on if you have specially needs or interactions you need to be sure are prevented while a process occurrs.
-
As we know that default is "read commited". but if your front end issuing some adhoc/dynamic sql statements/queries with isolation level, then it depends what isolation level is been used. suppose if 2 different user updating rows where user 'A' is using "SERIALIZABLE" & user 'B' is using 'Locking Hints" then user 'B' gets priority over 'A'. So it is very important to carefully consider the isolation levels on adhoc/dynamica sql statements. i hope this helps.
-
Never trust a default. It may change in time .....
afaik .net framework uses repeatable read by default. or at least, that's what I seem to notice when we implement a new .net application. Most of the time developers forget to specify "read committed"
Always define to connect using "read committed", unless there are other needs (more or less restrictive ... think of the consequences)
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply