Take that same users table where you have an occasionally query in serializable mode that hits the table. If every query running against the system was running in serializable mode, then it would effectively be single threaded, assume you have to users attempting to log in to the system, they would in serializable mode have to run one after another until al complete, rather than all being able to hit the table at the same time to verify their login info.
Take the example of a table which has user login information that is frequently hit to validate user access and their ability to log into the system. Although there are rare occasions where this may be the desired effect, most of the time serializable mode is an undesirable thing. If a transaction that is running in Serializable mode accesses or changes tables then those tables remain locked until the transaction completes.
#Read committed isolation level sql server 2012 serial#
“A serial execution is one in which each SQL-transaction executes to completion before the next SQL-transaction begins.” You can see how that would slow things down. Here is a brief explanation of the Serializable isolation level.
0 kommentar(er)
