Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Whenever I change the isolation level from read committed to re uncommitted. Then I restart the SQL Server Service (2005) it will reset the isolation level back to read committed.
Is there a way to stop this from happening? (changing the value on restart of SQL Server)
Isolation level can only be set within a connection. Simply reconnecting and it will change it back to the default. An application should always explicitly set the desired isolation level if not happy with the default. The default cannot be changed.
That being said, read uncommitted is never a good isolation level, because it produces inconsistent results. Whenever an application abuses the uncommitted isolation level is an indication of an access problem (like missing indexes leading to table scans).