interesting behavior I observed - database A has snapshot isolation level enabled and database B does not.
A transaction starts in database A and have few joins to database B. We got error `Snapshot isolation transaction failed accessing database 'database B' because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation`.
Interestingly, we got error for only few mins and then it went away. sys.dm_exec_requests shows that the transaction had read committed and it switched to snapshot on the db that does not have that isolation level enabled and …