Never heard of it before, Isolation Levels. But it makes sense since after some good reading.
As MSDN states: ‘…Transactions specify an isolation level that defines the degree to which one transaction must be isolated from resource or data modifications made by other transactions…’.
Wikipedia explains it quite nice: ‘…isolation determines how transaction integrity is visible to other users and systems. For example, when a user is creating a Purchase Order and has created the header, but not the PO lines, is the header available for other systems/users, carrying out concurrent operations (such as a report on Purchase Orders), to see?…’
Gavin Draper explains it as well on his blog with an example as well, to be found here.
SCOM 2012x & changing isolation levels
Apparently Microsoft Customer Support Services got this question in relation to SCOM 2012 R2 and whether those isolation levels can be changed. Microsoft found the answer to that question and decided to share it with the rest of the world on the SCOM Engineering blog, to be found here.