What is the best practice for the SNAPSHOT_ISOLATION parameter?


One of our customers is trying to apply all the best practices from the TRIRIGA documentation with different recommendations. One of them is regarding:

  • ALLOW_SNAPSHOT_ISOLATION: SET ALLOW_SNAPSHOT_ISOLATION should be set to ON
  • READ_COMMITTED_SNAPSHOT: SET READ_COMMITTED_SNAPSHOT should be set to ON

Their database department is telling them that if they activate this parameter, they could be doing “dirty reads”. Mainly, if they read and modify in the same tables at the same time. They said that other products control this situation. They wanted to know if TRIRIGA controls it. In case that TRIRIGA controls these situations, they will change it. Can you please confirm if they should set this parameter to ON?

TRIRIGA controls data integrity within the context of the web application. These settings for MS SQL make it behave more like Oracle and DB2, and we recommend that they be set to ON.

Continue reading

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s