Thresholds in SAP ASE

    By: Jeffrey Ross Garbus on Feb 02, 2014

    In this article, Alvin Chang along with Jeff Garbus and Lyle Fernquist discuss the importance of thresholds and how to configure them so that you can maintain a smooth operating database.

    One of the primary issues that can concern a DBA is the use of space in a database. This is a high priority since if space is not available to the database or the log database operations can stop. Or at least modifications to the database will stop. Whether the database is a user database, system database, or one of the tempdb databases, ensuring a database does not run out of space is vital to maintaining a smoothly operating application.

    ASE uses thresholds to help automate processes for database segments. A threshold is simply a space marker placed on a segment. When the space marker is reached, an action will be performed on the server. This action can be something as simple as printing a message on a console or logging a message to the errorlog to something more complicated like sending an email or running a dump tran command.

    While Adaptive Server allows for the creation of many thresholds the first threshold to be discussed will be the last. There is a point on the logsegment where SAP ASE determines that there are just enough pages to complete one last backup before running out of space. This is referred to as the “last chance thresh old.” This is a calculated point in the logsegment and cannot be manually configured. When this space marker is crossed two things will happen


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

    Released: February 2, 2014, 10:40 am | Updated: March 5, 2014, 11:05 am
    Keywords: ASE DBA Article | Technical Journal | Alvin Chang | ASE | Thresholds




    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