Knowledge (XXG)

Transaction log

Source đź“ť

952: 962: 243: 972: 50: 358:
notes that a checkpoint has been made. These are used to speed up recovery. They record information that eliminates the need to read a long way into the log's past. This varies according to checkpoint algorithm. If all dirty pages are flushed while creating the checkpoint (as in
332:(CLR) notes the rollback of a particular change to the database. Each corresponds with exactly one other Update Log Record (although the corresponding update log record is not typically stored in the Compensation Log Record). It includes this extra information: 200: 369:: This is a reference to the first log record that corresponds to a dirty page. i.e. the first update that wasn't flushed at checkpoint time. This is where redo must begin on recovery. 562: 195:(LSN): A unique ID for a log record. With LSNs, logs can be recovered in constant time. Most LSNs are assigned in monotonically increasing order, which is useful in recovery 545: 557: 375:: This is a reference to the oldest log record of the oldest in-progress transaction. This is the oldest log record needed to undo all in-progress transactions. 158:. Additionally, all transactions that are already committed but whose changes were not yet materialized in the database are re-applied. Both are done to ensure 477:
techrepublic.com, Understanding the importance of transaction logs in SQL Server, SQL Server transaction log maintenance, By Crowe, Chizek, November 11, 2004
996: 955: 324:: Includes the value of the bytes of page before and after the page change. Some databases may have logs which include one or both images. 628: 517: 476: 295:
All log records include the general log attributes above, and also other attributes depending on their type (which is recorded in the
975: 282: 487: 260: 1001: 681: 932: 579: 398: 264: 143: 871: 163: 338:: This field contains the LSN of the next log record that is to be undone for transaction that wrote the last Update Log. 159: 897: 616: 820: 810: 586: 413: 177: 151: 124: 253: 1006: 907: 640: 147: 38: 866: 856: 510: 569: 383:
notes that all work has been done for this particular transaction. (It has been fully committed or aborted)
937: 892: 435: 408: 912: 666: 465: 965: 902: 784: 754: 623: 574: 155: 466:
sqlshack.com, A beginner’s guide to SQL Server transaction logs, February 11, 2014 by Ivan Stankovic
922: 815: 800: 727: 552: 418: 146:
state or not been shut down properly, the database management system reviews the database logs for
917: 861: 830: 779: 611: 503: 671: 737: 591: 132: 927: 774: 764: 732: 100: 31: 835: 805: 540: 454: 887: 825: 769: 742: 635: 596: 990: 706: 691: 403: 136: 393: 75: 17: 228:
Information about the actual changes that triggered the log record to be written.
209:: A link to their last log record. This implies database logs are constructed in 696: 676: 242: 210: 840: 749: 711: 686: 495: 360: 306:
notes an update (change) to the database. It includes this extra information:
196: 64: 701: 656: 526: 423: 170: 96: 60: 267: in this section. Unsourced material may be challenged and removed. 606: 219:: A reference to the database transaction generating the log record. 139:
listing changes to the database, stored in a stable storage format.
601: 661: 128: 499: 318:: Length in bytes and offset of the page are usually included. 236: 180:, a journal is the record of data altered by a given process. 43: 30:"Binary log" redirects here. For the logarithm to base 2, see 352:
notes a decision to abort and hence roll back a transaction.
169:
This term is not to be confused with other, human-readable
27:
History of actions executed by a database management system
37:"Journal (computing)" redirects here. For other uses, see 71: 173:
that a database management system usually provides.
880: 849: 793: 720: 649: 533: 312:: A reference to the Page ID of the modified page. 142:If, after a start, the database is found in an 511: 135:or hardware failures. Physically, a log is a 8: 225:: Describes the type of database log record. 455:Microsoft, The Transaction Log (SQL Server) 518: 504: 496: 346:notes a decision to commit a transaction. 283:Learn how and when to remove this message 123:) is a history of actions executed by a 447: 188:A database log record is made up of: 7: 265:adding citations to reliable sources 971: 25: 184:Anatomy of a general database log 970: 960: 951: 950: 241: 48: 961: 252:needs additional citations for 399:Error correction and detection 63:format but may read better as 1: 233:Types of database log records 997:Database management systems 527:Database management systems 178:database management systems 1023: 933:Object–relational database 414:Log-structured file system 154:the changes made by these 125:database management system 36: 29: 946: 908:Federated database system 641:Blockchain-based database 39:Journal (disambiguation) 330:Compensation Log Record 322:Before and After Images 72:converting this article 1002:Transaction processing 938:Transaction processing 893:Database normalization 836:Query rewriting system 436:Federal Standard 1037C 409:Journaling file system 299:attribute, as above). 913:Referential integrity 488:neurobs.com, Logfiles 363:), it might contain: 217:Transaction ID number 903:Distributed database 261:improve this article 923:Relational calculus 801:Concurrency control 419:Write-ahead logging 193:Log Sequence Number 109:transaction journal 18:Journal (computing) 918:Relational algebra 862:Query optimization 667:Armstrong's axioms 127:used to guarantee 74:, if appropriate. 984: 983: 592:Wide-column store 587:Document-oriented 381:Completion Record 356:Checkpoint Record 316:Length and Offset 304:Update Log Record 293: 292: 285: 166:of transactions. 150:transactions and 93: 92: 16:(Redirected from 1014: 1007:Computer logging 974: 973: 964: 963: 954: 953: 928:Relational model 898:Database storage 775:Stored procedure 520: 513: 506: 497: 490: 485: 479: 474: 468: 463: 457: 452: 288: 281: 277: 274: 268: 245: 237: 131:properties over 101:computer science 95:In the field of 88: 85: 79: 70:You can help by 52: 51: 44: 32:Binary logarithm 21: 1022: 1021: 1017: 1016: 1015: 1013: 1012: 1011: 987: 986: 985: 980: 942: 888:Database models 876: 845: 831:Query optimizer 806:Data dictionary 789: 760:Transaction log 716: 672:Codd's 12 rules 645: 575:Column-oriented 541:Object-oriented 529: 524: 494: 493: 486: 482: 475: 471: 464: 460: 453: 449: 444: 432: 390: 289: 278: 272: 269: 258: 246: 235: 186: 105:transaction log 89: 83: 80: 69: 53: 49: 42: 35: 28: 23: 22: 15: 12: 11: 5: 1020: 1018: 1010: 1009: 1004: 999: 989: 988: 982: 981: 979: 978: 968: 958: 947: 944: 943: 941: 940: 935: 930: 925: 920: 915: 910: 905: 900: 895: 890: 884: 882: 881:Related topics 878: 877: 875: 874: 869: 864: 859: 857:Administration 853: 851: 847: 846: 844: 843: 838: 833: 828: 826:Query language 823: 818: 813: 808: 803: 797: 795: 791: 790: 788: 787: 782: 777: 772: 767: 762: 757: 752: 747: 746: 745: 740: 735: 724: 722: 718: 717: 715: 714: 709: 704: 699: 694: 689: 684: 679: 674: 669: 664: 659: 653: 651: 647: 646: 644: 643: 638: 633: 632: 631: 621: 620: 619: 609: 604: 599: 594: 589: 584: 583: 582: 572: 567: 566: 565: 560: 550: 549: 548: 537: 535: 531: 530: 525: 523: 522: 515: 508: 500: 492: 491: 480: 469: 458: 446: 445: 443: 440: 439: 438: 431: 428: 427: 426: 421: 416: 411: 406: 401: 396: 389: 386: 385: 384: 378: 377: 376: 370: 353: 347: 341: 340: 339: 327: 326: 325: 319: 313: 291: 290: 249: 247: 240: 234: 231: 230: 229: 226: 220: 214: 204: 185: 182: 91: 90: 56: 54: 47: 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 1019: 1008: 1005: 1003: 1000: 998: 995: 994: 992: 977: 969: 967: 959: 957: 949: 948: 945: 939: 936: 934: 931: 929: 926: 924: 921: 919: 916: 914: 911: 909: 906: 904: 901: 899: 896: 894: 891: 889: 886: 885: 883: 879: 873: 870: 868: 865: 863: 860: 858: 855: 854: 852: 848: 842: 839: 837: 834: 832: 829: 827: 824: 822: 819: 817: 814: 812: 809: 807: 804: 802: 799: 798: 796: 792: 786: 783: 781: 778: 776: 773: 771: 768: 766: 763: 761: 758: 756: 753: 751: 748: 744: 741: 739: 736: 734: 731: 730: 729: 726: 725: 723: 719: 713: 710: 708: 707:Surrogate key 705: 703: 700: 698: 695: 693: 692:Candidate key 690: 688: 685: 683: 680: 678: 675: 673: 670: 668: 665: 663: 660: 658: 655: 654: 652: 648: 642: 639: 637: 634: 630: 627: 626: 625: 622: 618: 615: 614: 613: 610: 608: 605: 603: 600: 598: 595: 593: 590: 588: 585: 581: 578: 577: 576: 573: 571: 568: 564: 561: 559: 556: 555: 554: 551: 547: 544: 543: 542: 539: 538: 536: 532: 528: 521: 516: 514: 509: 507: 502: 501: 498: 489: 484: 481: 478: 473: 470: 467: 462: 459: 456: 451: 448: 441: 437: 434: 433: 429: 425: 422: 420: 417: 415: 412: 410: 407: 405: 404:Hash function 402: 400: 397: 395: 392: 391: 387: 382: 379: 374: 371: 368: 365: 364: 362: 357: 354: 351: 348: 345: 344:Commit Record 342: 337: 334: 333: 331: 328: 323: 320: 317: 314: 311: 308: 307: 305: 302: 301: 300: 298: 287: 284: 276: 266: 262: 256: 255: 250:This section 248: 244: 239: 238: 232: 227: 224: 221: 218: 215: 212: 208: 205: 202: 198: 194: 191: 190: 189: 183: 181: 179: 174: 172: 167: 165: 161: 157: 153: 149: 145: 140: 138: 134: 130: 126: 122: 118: 114: 110: 106: 102: 98: 87: 78:is available. 77: 73: 67: 66: 62: 57:This article 55: 46: 45: 40: 33: 19: 759: 483: 472: 461: 450: 394:Data logging 380: 372: 366: 355: 350:Abort Record 349: 343: 335: 329: 321: 315: 309: 303: 296: 294: 279: 270: 259:Please help 254:verification 251: 222: 216: 206: 192: 187: 175: 168: 156:transactions 144:inconsistent 141: 120: 116: 113:database log 112: 108: 104: 94: 81: 76:Editing help 58: 976:WikiProject 867:Replication 755:Transaction 697:Foreign key 677:CAP theorem 624:Multi-model 336:undoNextLSN 211:linked list 148:uncommitted 121:audit trail 991:Categories 841:Query plan 794:Components 712:Unique key 629:comparison 563:comparison 553:Relational 546:comparison 442:References 361:PostgreSQL 197:algorithms 164:durability 152:rolls back 117:binary log 850:Functions 785:Partition 612:In-memory 570:Key–value 273:July 2016 160:atomicity 97:databases 84:June 2015 956:Category 872:Sharding 728:Relation 702:Superkey 657:Database 650:Concepts 424:Redo log 388:See also 207:Prev LSN 966:Outline 765:Trigger 721:Objects 430:Sources 373:undoLSN 367:redoLSN 199:, like 133:crashes 780:Cursor 738:column 607:NewSQL 310:PageID 107:(also 59:is in 770:Index 733:table 636:Cloud 602:NoSQL 597:Graph 534:Types 213:form. 201:ARIES 65:prose 821:ODBC 811:JDBC 750:View 687:Null 682:CRUD 662:ACID 617:list 580:list 558:list 297:Type 223:Type 171:logs 162:and 137:file 129:ACID 103:, a 61:list 816:XQJ 743:row 263:by 176:In 119:or 99:in 993:: 115:, 111:, 519:e 512:t 505:v 286:) 280:( 275:) 271:( 257:. 203:. 86:) 82:( 68:. 41:. 34:. 20:)

Index

Journal (computing)
Binary logarithm
Journal (disambiguation)
list
prose
converting this article
Editing help
databases
computer science
database management system
ACID
crashes
file
inconsistent
uncommitted
rolls back
transactions
atomicity
durability
logs
database management systems
algorithms
ARIES
linked list

verification
improve this article
adding citations to reliable sources
Learn how and when to remove this message
PostgreSQL

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑