Transaction Log Management

    By: Jeffrey Ross Garbus on Jul 01, 2013

    One significant aspect of working with SAP Sybase ASE is understanding the transaction log and how it actually works with the database.

    The transaction log is the repository for all data changes in the database. When new data is inserted via an INSERT command, removed with a DELETE statement, or modified with an UPDATE statement, the information related to the data changes made by that command is recorded in the transaction log in memory and then pushed to disk prior to the client receiving the confirmation of the commit (the commit is the feedback that the write to the transaction log was successful). When the ASE server is restarted, each database undergoes the recovery process, which is the process of determining whether a transaction completed or not, based upon what is stored within the transaction log.

    For a transactionally active database the transaction log can fill up very quickly with data changes unless it is properly maintained. On the opposite side of the spectrum, if the wrong choice of maintenance plan is selected for a database, data recovery from a disaster can be compromised.

    Login to read the article. Not a member? Create a free account!

    Released: July 1, 2013, 7:05 am | Updated: January 27, 2014, 7:18 pm
    Keywords: ASE DBA Article | Technical Journal | Alvin Chang | Data Management | Jeff Garbus | Lyle Fernquist | Transaction Log


     

     

    TwitterLLinkedinLFacebook

    Copyright © 2014 ISUG-TECH. All Rights Reserved
    All material, files, logos and trademarks within this site are copyright their respective organizations

    Terms of Service - Privacy Policy - Contact the Help Desk