'Declaration Public Property ConcurrentAccessResolution As String
public string ConcurrentAccessResolution {get; set;}
'Declaration Public Property ConcurrentAccessResolution As String
public string ConcurrentAccessResolution {get; set;}
Available modes:
| Value | Description |
|---|---|
| "0" or no value | The currently committed behavior is determined by the database configuration. Default value. |
| CurrentlyCommitted | The database manager can use the currently committed version of the data for applicable scans when the data is in the process of being updated or deleted. Rows in the process of being inserted can be skipped. This setting applies when the isolation level in effect is Cursor Stability or Read Stability (for Read Stability it skips uncommited inserts only) and is ignored otherwise. Applicable scans include read-only scans that can be part of a read-only statement as well as a non read-only statement. The settings for the DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED registry variables do not apply to scans using currently committed. However, the settings for these registry variables still apply to scans that do not use currently committed. |
| WaitForOutcome | Cursor Stability and higher scans wait for the commit or rollback when encountering data in the process of being updated or deleted. Rows in the process of being inserted are not skipped. The settings for the DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED registry variables no longer apply. |
| SkipLockedData | Currently committed semantics are used and rows in the process of being inserted are skipped. This option is not supported on DB2 for Linux, UNIX, and Windows. If specified, this setting is ignored. |
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2