zoukankan      html  css  js  c++  java
  • SQL Server does not purge row versioning records even the transaction are committed if there are other open transaction running in the databases with read-committed snapshot enabled .

    This is a by-design behavior. There is only one allocation unit in tempdb that is
    tracking the versioned records across the server. Cleanup of this allocation
    unit is decided by the oldest transaction of READ_COMMITTED_SNAPSHOT enabled
    database.  SQL Server won’t remove row
    versioning records of all databases greater than the oldest transaction until
    it commits or rollback.

    Here is an example

    Database db1 and db2 have read_committed_snapshot enabled.

    1)session 1

    use db1

    begin tran

    select *From table1DB1

     

    2)session 2

    use db2

    update table1DB2 set c1=c1+1

     

    Then the SQL Server does not remove the row versioning records of session 2 until session 1 transaction commit rollback.

     

    Then we start an new transaction

    3)Session 3

    use db1

    begin tran

    select * from table2DB1

     

    4)Session 4

    use db2

    update table1DB2 set c1=c1+1

     

     

    if Session 1 is commit right now.

    The row versioning records of session 2 will be removed by SQL Server.

    However,The row versioning records of session 4 will not be removed by SQL Server, because transaction in session 3 is still there.

  • 相关阅读:
    CodeForces
    CodeForces-1253B(贪心+模拟)
    WebFlux、Reactive编程特性
    redis-on-windows配置解释
    SpringBoot配置方式补充
    如何在 Ubuntu 20.04 上安装 Python Pip
    MySQL之1055错误
    CuckooSandbox
    Manjaro 20.0.1 Lysia 安装Googlepinyin
    Manjaro 20.0.1 Lysia 更新国内镜像源
  • 原文地址:https://www.cnblogs.com/stswordman/p/10416191.html
Copyright © 2011-2022 走看看