About 1,260,000 results
Open links in new tab
  1. SQL Server transaction log architecture and management guide

    Nov 22, 2024 · Understanding the architecture can improve your effectiveness in managing transaction logs. The SQL Server transaction log operates logically as if the transaction log is a string of log records. Each log record is identified by a log sequence number (LSN).

  2. SQL Server Transaction Log Architecture - SQL Shack

    Jan 31, 2019 · This article will cover SQL Server transaction log architecture including file topography, basic overview, review of LSN and MinLSN, and log truncation

  3. SQL Server transaction log architecture - Simple Talk - Redgate …

    Jun 8, 2021 · As a DBA, you need to understand the architecture of the transaction log, how to manage the size and growth of the log, and periodically take transaction log backups of databases that are not in simple recovery mode.

  4. SQL Server Transaction Log and Recovery Models - SQL Shack

    In this article, we will go through the relationship between the SQL Server Transaction Log and the three database recovery models. A recovery model is a database property that defines how the SQL Server Engine treats the database transaction logs including.

  5. The SQL Server Transaction Log, Part 2: Log Architecture

    Feb 1, 2022 · Figure 1: The three-level structural hierarchy of the transaction log. The transaction log contains virtual log files, which contain log blocks, which store the actual log records. The transaction log is split up into sections called virtual log files, commonly just called VLFs.

  6. Understanding SQL Server Transaction Log File Architecture

    Jul 24, 2017 · SQL Server uses transaction log file to capture log records that guarantee the data integrity of the database and for data recovery. Logically, SQL Server transaction log is a string of log records. Each log record is identified by a log sequence number (LSN).

  7. There is no specific formula for how many VLFs you should have in your log file. Too many leads to fragmentation. Too few leads to large VLFs and slow performance. The goal is to have your log be as large as necessary, with a reasonable autogrowth increment (example: 128 MB).

  8. SQL Server Transaction Log – Part 1 – Log Structure and Write …

    Dec 18, 2014 · Every SQL database has a transaction log which maps over one or more physical files. The Database Engine divides each file into a specific number of virtual log files (VLFs) that are being used to hold the information about everything happening inside our databases. This number of VLFs is not some kind of magic but it is being chosen dynamically.

  9. SQL SERVER – Basic architecture of Transaction Logs

    Sep 28, 2015 · The SQL Server transaction log operates logically as if the transaction log is a string of log records. Each log record is identified by a log sequence number (LSN). Each new log record is written to the logical end of the log with an LSN …

  10. Log File Architecture in SQL Server - sqldbanow.com

    Below is the process how a query is processed in SQL Server/ Importance of Log File Architecture: Database has Data file and Log file. The query statement is passed to the buffer cache and log cache. The data in the buffer cache is called as Dirty Data or Dirty Blocks.

  11. Some results have been removed
Refresh