[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 830
  • Last Modified:

Default Isolation Level in SQL Server 2000?

I got this wiered error today in my Production. Suddenly at 3 PM there was Assertion file created in error log, than there was RID error( Index not able to locate the page....although DBCC showed no errors for Indexes) and than Database suddenly went into SUSPECT MODE....We had to restore the Database with Point-In-Time................but when I went through microsoft articles.......it states that RID error is SQL Server SP3a Bug which was rectified in SP4.......
THis situation occurs when query is using Transaction Level as READ UNCOMMITTED at the same time other query is Deleting the same row data....
MY QUESTION HERE IS SIMPLE.....WHAT IS THE DEFAULT ISOLATION LEVEL FOR SQL SERVER 2000???
IF SOMEBODY CAN HELP ME ANALZYE THIS ERROR IT WILL BE GREAT HELP.....
0
GEEK_SQL
Asked:
GEEK_SQL
1 Solution
 
dportasCommented:
READ COMMITTED is the default.

What level is your server patched to? I suggest you consider installing SP4 if you haven't already.
0
 
GEEK_SQLAuthor Commented:
Server has Sp3a installed and we are in process of installing Service Pack 4.
I just had one query, if READ COMMITTED is Default and what could be the possible reason for us to get this error, which is related to READ UNCOMMITTED error.....here is the article attached from Microsoft which describes about this Bug.......we are seeing exact errors in our Envr.
http://support.microsoft.com/kb/834290 
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now