Symptom
SQL Server has five types of transaction isolation levels: Read Uncommitted, Read Committed, Repeatable Read, Serializable and Snapshot. And the default transaction isolation level is Read Committed. For NETWEAVER based applications, SAP recommends customer keeping this default setting. Please don't change it.
However, some customer run the following command "DBCC useroptions" on T_code DBAcockpit =>Diagnostics =>SQL Command Editor from a SAP Netweaver system, and get the following result:
Set Option Value
======================================================
textsize 2147483647
language us_english
dateformat mdy
datefirst 7
lock_timeout -1
quoted_identifier SET
ansi_null_dflt_on SET
ansi_warnings SET
ansi_padding SET
ansi_nulls SET
concat_null_yields_null SET
isolation level read uncommitted
The isolation level is different from SAP recommendation and also different from the execution result with the same command from SQL Server Management Studio:
Set option Value
textsize -1
language us_english
dateformat mdy
datefirst 7
lock_timeout -1
quoted_identifier SET
ansi_null_dflt_on SET
ansi_warnings SET
ansi_padding SET
ansi_nulls SET
concat_null_yields_null SET
isolation level read committed
The result of isolation level is different for these two checking means.
Read more...
Environment
SQL Server 2005 and Higher
SQL Server based SAP ABAP system
Product
Keywords
SQL Server Isolation Level Read Committed Read Uncommitted DBCC Useroptions , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.