DOCSLIB.ORG

Log Shipping

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Log Shipping Log Shipping LS 1. Log Shipping Configuration? A: Permissions To setup a log-shipping you must have sysadmin rights on the server. Minimum Requirements 1. SQL Server 2005 or later 2. Standard, Workgroup or Enterprise editions must be installed on all server instances involved in log shipping. 3. The servers involved in log shipping should have the same case sensitivity settings. 4. The database must use the full recovery or bulk-logged recovery model 5. A shared folder for copying T-Log backup files 6. SQL Server Agent Service must be configured properly In addition, you should use the same version of SQL Server on both ends. It is possible to Log Ship from SQL 2005 to SQL 2008, but you can not do it the opposite way. Also, since Log Shipping will be primarly used for failover if you have the same versions on each end and there is a need to failover you at least know you are running the same version of SQL Server. Steps to Configure Log-Shipping: 1. Make sure your database is in full or bulk-logged recovery model. You can change the database recovery model using the below query. You can check the database recovery model by querying sys.databases SELECT name, recovery_model_desc FROM sys.databases WHERE name = 'jugal' USE [master] GO ALTER DATABASE [jugal] SET RECOVERY FULL WITH NO_WAIT GO 2. On the primary server, right click on the database in SSMS and select Properties. Then select the Transaction Log Shipping Page. Check the "Enable this as primary database in a log shipping configuration" check box. 3. The next step is to configure and schedule a transaction log backup. Click on Backup Settings… to do this. If you are creating backups on a network share enter the network path or for the local machine you can specify the local folder path. The backup compression feature was introduced in SQL Server 2008 Enterprise edition. While configuring log shipping, we can control the backup compression behavior of log backups by specifying the compression option. When this step is completed it will create the backup job on the Primary Server. 4. In this step we will configure the secondary instance and database. Click on the Add… button to configure the Secondary Server instance and database. You can add multiple servers if you want to setup one to many server log-shipping. When you click the Add… button it will take you to the below screen where you have to configure the Secondary Server and database. Click on the Connect… button to connect to the secondary server. Once you connect to the secondary server you can access the three tabs as shown below. Initialize Secondary Database tab In this step you can specify how to create the data on the secondary server. You have three options: create a backup and restore it, use an existing backup and restore or do nothing because you have manually restored the database and have put it into the correct state to receive additional backups. Copy Files Tab In this tab you have to specify the path of the Destination Shared Folder where the Log Shipping Copy job will copy the T-Log backup files. This step will create the Copy job on the secondary server. Restore Transaction Log Tab Here you have to specify the database restoring state information and restore schedule. This will create the restore job on the secondary server. 5. In this step we will configure Log Shipping Monitoring which will notify us in case of any failure. Please note Log Shipping monitoring configuration is optional. Click on Settings… button which will take you to the “Log Shipping Monitor Settings” screen. Click on Connect …button to setup a monitor server. Monitoring can be done from the source server, target server or a separate SQL Server instance. We can configure alerts on source / destination server if respective jobs fail. Lastly we can also configure how long job history records are retained in the MSDB database. Please note that you cannot add a monitor instance once log shipping is configured. 6. Click on the OK button to finish the Log Shipping configuration and it will show you the below screen. 2. How to Reverse Log Shipping Roles Reversing log shipping is an often overlooked practice. When DBAs need to fail over to a secondary log shipping server, they tend to worry about getting log shipping back up later. This is especially true in the case of very large databases. If you're using log shipping as your primary disaster recovery solution and you need to fail over to the secondary log shipping server, you should get log shipping running as quickly as possible. With no disaster recovery failover in place, you might be running exposed. Reversing log shipping is simple. It doesn’t require reinitializing the database with a full backup if performed carefully. However, it’s crucial that you remember the following: You need to preserve the log sequence number (LSN) chain. You need to perform the final log backup using the NORECOVERY option. Backing up the log with this option puts the database in a state that allows log backups to be restored and ensures that the database’s LSN chain doesn’t deviate. The primary log shipping server must still be accessible to use this technique. To fail over to a secondary log shipping server, follow this 10-step process: 1. Disable all backup jobs that might back up the database on both log shipping partners. 2. Disable the log shipping jobs. 3. Run each log shipping job in order (i.e., backup, copy, and restore). 4. Drop log shipping. 5. Manually back up the log of the primary database using the NORECOVERY option. Use the command BACKUP LOG [DatabaseName] TO DISK = 'BackupFilePathname' WITH NORECOVERY; where DatabaseName is the name of the database whose log you want to back up and BackupFilePathname is the backup file’s pathname (e.g., Z:\SQLServerBackups\TLog.bck). 6. Restore the log backup on the secondary database using the RECOVERY option, and bring the secondary database online. The primary and secondary databases have now switched positions. 7. Back up the log of the new primary database (optional). 8. Restore the log on the new secondary database using the NORECOVERY option (optional). 9. Reconfigure log shipping. 10. Re-enable any backup jobs that were disabled. Note that step 7 and step 8 are listed as optional because they’re not required for establishing log shipping. However, I recommend performing these steps to ensure that the log shipping configuration will proceed without any problems. With a few minor adjustments, this 10-step process works with multiple secondary log shipping databases. You perform the same basic steps, keeping in mind that the other secondary databases will still be secondary databases after the failover. After you back up the log on the new primary database, you should use the NORECOVERY option to restore that backup on all the planned secondary databases. You can then add them as secondary databases to the new primary database. 3. Is it possible configuration of log shipping without domain? You could try to move the logs using FTP then you don't need a domain account for the copy just FTP access 4. What is TUF? A: TOUF file is known as transaction undo file This file is created when logshipping is configured in SQL Server This is consists of list of uncommitted transactions while backup is going on the primary server in logshipping. if this is deleted you have to reconfigure the logshipping as the secondary server. This file is located in the path where transaction log files are saved. .TUF file is the Transaction Undo File, which is created when performing log shipping to a server in Standby mode. When the database is in Standby mode the database recovery is done when the log is restored; and this mode also creates a file on destination server with .TUF extension which is the transaction undo file. This file contains information on all the modifications performed at the time backup is taken. The file plays a important role in Standby mode… the reason being very obvious while restoring the log backup all uncommited transactions are recorded to the undo file with only commited transactions written to disk which enables the users to read the database. So when we restore next transaction log backup; SQL server will fetch all the uncommited transactions from undo file and check with the new transaction log backup whether commited or not. If found to be commited the transactions will be written to disk else it will be stored in undo file until it gets commited or rolledback. 5. What is TUF file? The transaction undo file contains modifications that were not committed on the source database but were in progress when the transaction log was backed up AND when the log was restored to another database, you left the database in a state that allowed addition transaction log backups to be restored to it (at some point in the future. When another transaction log is restored, SQL Server uses data from the undo file and the transaction log to continue restoring the incomplete transactions (assuming that they are were completed in the next transaction log file). Following the restore, the undo file will be re-written with any transactions that, at that point, are incomplete. TUF file is known as "Transaction Undo File" This file is created when LogShipping is configured in SQL Server. This file consists of list of uncommitted transactions while backup is going on the primary server in Log Shipping.
Load more

Recommended publications
  • RDBMS in the Cloud: Deploying SQL Server on AWS
    RDBMS in the Cloud: Deploying SQL Server on AWS Darryl Osborne Vlad Vlasceanu June 2015 Amazon Web Services – RDBMS in the Cloud: Deploying SQL Server on AWS May 2015 © 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Page 2 of 67 Amazon Web Services – RDBMS in the Cloud: Deploying SQL Server on AWS May 2015 Contents Abstract 5 SQL Server Solutions on AWS 6 Amazon RDS for SQL Server 6 SQL Server on Amazon EC2 6 Hybrid Scenarios 7 Choosing between SQL Server Solutions on AWS 7 Amazon RDS for SQL Server 9 Starting a Microsoft SQL Server RDS Instance 11 Security 15 Performance Management 19 High Availability 26 Monitoring and Management 27 Managing Cost 30 SQL Server on Amazon EC2 33 Starting a Microsoft SQL Server Instance 33 Security 38 Performance Management 40 High Availability 44 Monitoring and Management 48 Managing Cost 49 Caching 52 Hybrid Scenarios 53 Backups to the Cloud 53 SQL Server Log Shipping – Between On-Premises and Amazon EC2 57 Page 3 of 67 Amazon Web Services – RDBMS in the Cloud: Deploying SQL Server on AWS May 2015 SQL Server AlwaysOn Availability Groups – Between On-Premises and Amazon EC2 58 Amazon RDS Migration Tool 59 Conclusion 60 Further Reading 61 Appendix 62 I.
    [Show full text]
  • Aptum Database Administration Program September 2019 Overview
    SERVICE GUIDE APTUM DATABASE ADMINISTRATION PROGRAM SEPTEMBER 2019 OVERVIEW Aptum’s Database Administration (DBA) Program was designed to DBA Plan hours can be leveraged for all database-related activities help our customers reduce the cost of normal operation and the risk of detailed within this document, up to the allocation purchased. If you application and database downtime. require more hours than are purchased in a plan for a given month, any excess will be billed on an hourly basis at the standard Database Customers can work with Aptum’s Solutions Engineers and Certified Administration rate. Database Administrators to obtain assistance with everything from database engine configuration, performance optimization, clustering Included Database Platforms: administration, and replication administration. Microsoft SQL Server To help you achieve your performance goals, we offer our DBA plans in MySQL/MariaDB/Percona block-hour increments: 4 hours* * Hours are monthly and renew at the 1st of each calendar month and do not roll over. Overage rates are applicable only after block hours are consumed. All hours are 8 hours* applicable to the entire solution not per server. 12 hours* 20 hours* THE NEED FOR DATABASE ADMINISTRATION Most applications—especially those that support enterprise processes enable e-commerce, or facilitate collaboration—are database-intensive and demand optimal performance from the database. Applications and database queries may utilize very lean and elegant code, but the structure and configuration of your databases can be a detriment to high performance. There are dozens, sometimes hundreds, of configuration settings that need to be optimally tuned to enhance database performance. When the database is installed, most configuration defaults are applied automatically.
    [Show full text]
  • Deploying Microsoft SQL Server on Amazon Web Services
    Deploying Microsoft SQL Server on Amazon Web Services This paper has been archived. November 2019 For the latest technical content about the AWS Cloud, see the AWS Whitepapers & Guides page: https://aws.amazon.com/whitepapers Archived Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Archived Contents Introduction .......................................................................................................................... 1 Amazon RDS for SQL Server .......................................................................................... 1 SQL Server on Amazon EC2 ........................................................................................... 1 Hybrid Scenarios .............................................................................................................. 2 Choosing Between
    [Show full text]
  • Destiny® System Backups
    Destiny® system backups Establishing a backup and restore plan for Destiny Overview It is important to establish a backup and restore plan for your Destiny installation. The plan must be validated and monitored to ensure that your data is sufficiently backed up and can be recovered in the event of hardware failure or other disaster. IMPORTANT Follett recommends deploying a comprehensive backup solution and testing and monitoring all backup processes. There are tradeoff decisions to be made in the backup strategy that will be shaped by your organization’s risk tolerance, technology constraints, and ability to absorb data loss or downtime. This document provides an overview of standard backup and restore for the Destiny system. IMPORTANT This content does not cover high-availability configurations such as clustered servers or log shipping. Please contact Follett School Solutions, Inc. Technical Support should you have any questions about backing up your Destiny installation. For details, see Destiny® system backups. Backing up Destiny: an overview SQL database The heart of the Destiny data resides in the SQL database. These are the main components of SQL data to be backed up: The Destiny SQL database. This database contains the main Destiny data. Proper SQL backup configuration of this database is essential. NOTE If your installation is a consortium, you will have to ensure a proper backup of multiple SQL databases (one per member). The Destiny SQL transaction log. The Master SQL database. This system database is useful when restoring to a replacement server. It is not necessary to back up the tempdb database. This is a SQL Server work area and is recreated automatically.
    [Show full text]
  • SQL/Oracle Database Administrator Work Location: Brooklyn, NY
    City of New York Department of Information Technology and Telecommunications Job Posting Notice Civil Service Title: Certified IT Administrator (Database) Level: 03 Title Code No: 13644 Salary: $83,323/$95,821 - $110,000 Business Title: SQL/Oracle Database Administrator Work Location: Brooklyn, NY Division/Work Unit: IT Services Number of Positions: 5 Job ID: 249532 Hours/Shift: Day - Due to the necessary technical support duties of this position in a 24/7 operation, candidate may be required to work various shifts such as weekends and/or nights/evenings. Job Description DoITT provides for the sustained, efficient and effective delivery of IT services, infrastructure and telecommunications to enhance service delivery to New York City's residents, businesses, employees and visitors. As the City's technology leader, DoITT is responsible for maintaining the foundational IT infrastructure and systems that touch every aspect of City life from public safety to human services, from education to economic development crossing the full spectrum of governmental operations. The successful candidate will serve as an SQL/Oracle Database Administrator reporting to the IT Services Division. Responsibilities will include: Build and configure multiple MS SQL and Oracle databases, equally clustered, non-clustered and virtual environments for the DoITT Enterprise Content Management shared service implementation; develop, design, configure and document database architecture, including software, hardware and physical layout (Processor configurations, SAN luns,
    [Show full text]
  • Sql Server to Aurora Mysql Migration Playbook
    Microsoft SQL Server To Amazon Aurora with MySQL Compatibility Migration Playbook Version 1.8, September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 8 Tables of Feature Compatibility 11 AWS Schema and Data Migration Tools 23 AWS Schema Conversion Tool (SCT) 24 SCT Action Code Index 38 AWS Database Migration Service (DMS) 54 ANSI SQL 57 Migrate from SQL Server Constraints 58 Migrate to Aurora MySQL Constraints 62 Migrate from SQL Server Creating Tables 67 Migrate to Aurora MySQL Creating Tables 71 Migrate from SQL Server Common Table Expressions 77 Migrate to Aurora MySQL Common Table Expressions 80 Migrate from SQL Server Data Types 84 Migrate to Aurora MySQL Data
    [Show full text]
  • SAP HANA System Replication Company
    PUBLIC SAP HANA Platform 2.0 SPS 04 Document Version: 1.1 – 2019-10-31 SAP HANA System Replication company. All rights reserved. All rights company. affiliate THE BEST RUN 2019 SAP SE or an SAP SE or an SAP SAP 2019 © Content 1 SAP HANA System Replication..................................................6 2 SAP HANA System Replication: Basic Concepts.....................................8 2.1 Introduction.................................................................9 2.2 Replication Modes for SAP HANA System Replication...................................12 2.3 Operation Modes for SAP HANA System Replication....................................14 2.4 Data Transferred to the Secondary System..........................................16 2.5 Resync Optimization..........................................................19 Data Retention........................................................... 20 Log Retention............................................................20 2.6 Network Recommendations.....................................................27 Distance Between Data Centers............................................... 27 Network Throughput.......................................................28 Data and Log Compression...................................................30 Data and Log Volume Encryption...............................................31 2.7 Secondary System Usage...................................................... 31 3 SAP HANA System Replication: Configuration .....................................34 3.1 General Prerequisites
    [Show full text]
  • Litespeed for SQL Server
    LiteSpeed® for SQL Server® 8.7 Configure Log Shipping Guide © 2018 Quest Software Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc. The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice.
    [Show full text]
  • Salt Lake County Job Description Database Administrator
    Salt Lake County Job Description Database Administrator DEPARTMENT: Administrative Services DIVISION: Information Services / 6050 JOB CODE: 609-2 GRADE: 16 Center for the Arts/ 3500 SALARY PLAN: TRD FLSA STATUS: Exempt SAFETY SENSITIVE: No EFFECTIVE DATE: 12/06/2016 JOB SUMMARY Uses, maintains and develops databases within a wide range of public and private databases. Designs, implements and maintains all functions of database systems while maintaining database policies and procedures, data integrity, data extraction, report customization and analysis. MINIMUM QUALIFICATIONS Seven (7) years of experience in a closely related field; OR a Bachelor’s degree from an accredited college or university in Information Technology, or other closely related field, plus three (3) years of related experience.; Or an equivalent combination of education and experience. FOR DATABASE POSITIONS IN INFORMATION SERVICES PREFERRED CERTIFICATIONS: MCDBA, MTA(Data), MCSA(Data), MCSE(data) Due to the nature of this position, the successful applicant must pass a required pre-employment background check and subsequent mandatory background checks in accordance with current County Human Resources policy requirements. ESSENTIAL FUNCTIONS • Creates databases, configures and manages system database files. • Identifies available space on data volumes, identifies the cause of performance degradation. • Resolves backup/restore incidents. • Identifies problematic execution plans. • Monitors current sessions, identifies sessions that cause blocking activity, identifies sessions that consume resources, and configures the data collector. • Acts as a backup very large databases, configures alerting for failed backups, manages the process to back up database operating systems, manages transaction log backups, configures database recovery models, configures backup automation. • Configures an audit on SQL Server, queries the SQL Server audit log, and manages a SQL Server audit.
    [Show full text]
  • Query Fresh: Log Shipping on Steroids
    Query Fresh: Log Shipping on Steroids Tianzheng Wang Ryan Johnson Ippokratis Pandis University of Toronto LogicBlox Amazon Web Services [email protected] [email protected] [email protected] ABSTRACT to guarantee strong safety [20]: transactions are not committed Hot standby systems often have to trade safety (i.e., not losing com- until their log records are persisted in all (or a majority of) nodes. mitted work) and freshness (i.e., having access to recent updates) Synchronous log shipping ensures that if the primary fails, a backup for performance. Guaranteeing safety requires synchronous log can take over as the new primary without losing committed work. shipping that blocks the primary until the log records are durably In addition to replaying log records, backups can serve read-only replicated in one or multiple backups; maintaining freshness ne- transactions, improving resource utilization and performance. cessitates fast log replay on backups, but is often defeated by the 1.1 The Freshness Gap dual-copy architecture and serial replay: a backup must generate The ability to serve read-only transactions on backups while the “real” data from the log to make recent updates accessible to read-only queries. maintaining strong safety guarantees is a salient feature of log ship- This paper proposes Query Fresh, a hot standby system that pro- ping: modern database servers are high-end machines that constitute vides both safety and freshness while maintaining high performance non-trivial parts of the total cost of ownership, and offloading read- only transactions to backups can significantly increase hardware on the primary. The crux is an append-only storage architecture used in conjunction with fast networks (e.g., InfiniBand) and byte- utilization and read-only throughput.
    [Show full text]
  • SQL Server Interview Questions
    SQL Server interview questions Explain the use of keyword WITH ENCRYPTION. Create a Store Procedure with Encryption. It is a way to convert the original text of the stored procedure into encrypted form. The stored procedure gets obfuscated and the output of this is not visible to CREATE PROCEDURE Abc WITH ENCRYPTION AS << SELECT statement>> GO What is a linked server in SQL Server? It enables SQL server to address diverse data sources like OLE DB similarly. It allows Remote server access and has the ability to issue distributed queries, updates, commands and transactions. Features and concepts of Analysis Services Analysis Services is a middle tier server for analytical processing, OLAP, and Data mining. It manages multidimensional cubes of data and provides access to heaps of information including aggregation of data One can create data mining models from data sources and use it for Business Intelligence also including reporting features. Some of the key features are: • Ease of use with a lot of wizards and designers. • Flexible data model creation and management • Scalable architecture to handle OLAP • Provides integration of administration tools, data sources, security, caching, and reporting etc. • Provides extensive support for custom applications What is Analysis service repository? Every Analysis server has a repository to store metadata for the objects like cubes, data sources etc. It’s by default stored in a MS Access database which can be also migrated to a SQL Server database. What is SQL service broker? Service Broker allows internal and external processes to send and receive guaranteed, asynchronous messaging. Messages can also be sent to remote servers hosting databases as well.
    [Show full text]
  • Data Administration in Information Systems 2Nd Semester Lab 6: Recovery
    MEIC 2019/2020 Data Administration in Information Systems 2nd semester Lab 6: Recovery In this lab class we will approach the following topics: 1. Important Concepts 1.1. Transaction Logs and Recovery in SQL Server 1.2. WAL and ARIES-like logging and recovery scheme 1.3. SQL Server Restore Recovery Models 1.4. Disaster Recovery in SQL Server 2. Experiments and Exercises 2.1. Some Examples on Database Backups 2.2. Exercises 1.1. Transaction Logs and Recovery in SQL Server Every SQL Server database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a critical component of the database. If there is a system failure, the transaction log might be required to bring your database back to a consistent state. The transaction log supports the following operations: • Recovery of individual transactions in the case of a transaction rollback (undoing) • Recovery of all incomplete transactions when SQL Server is started (restart recovery) • Rolling a restored database, file, filegroup, or page forward to the point of failure (restore recovery) • Supporting transactional replication in multiple copies of the same database. If a computer that is running SQL Server fails, the databases may be left in a state where some modifications were never written from the buffer cache to the data files, and there may be some modifications from incomplete transactions in the data files. When an instance of SQL Server is started, it runs a recovery process of each database. Every modification recorded in the log, which may not have been written to the data files, is rolled forward.
    [Show full text]