Knowledge (XXG)

Transaction log

Source đź“ť

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

Index

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
Data logging

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

↑