0 MY CART
Added to Cart
    You have items in your cart
    You have 1 item in your cart
    Total
    Check Out Continue Shopping

    Utility Scripts

    Choose one or more.  All are priced at $0.00. Each underlined item selected will add to your cart for checkout Total Amount of $0.00.

    Prerequisite before use:
    GDPR Agreement. 
    I consent to having this website store my submitted information so they can respond to my inquiry    .
    To allow tracking of downloads to 'recently verified' email address we will add your email address to our marketing list.
    You will receive an email with the ability to download the file, usually in less than three minutes.

    Purpose:
    Helpful downloadable scripts and more to assist with MySQL use.
    There are also a few Excel spreadsheets for your use.

    DRVxPredFullDate.xls    < click to add to cart - then Checkout to complete 
    A way to Predict Full Date for a data drive ( or any drive ). As easy as recording
    Free Space, Total Size, Date, by to quickly get an idea when your drive may be FULL. Recording requirements, none. Quarterly (3 month interval) is recommended and File Save.

    findfragtables.sql   < click to add to cart - then Checkout to complete 
    If you knew the fragmented tables existed they could be managed on your schedule.
    Why are they fragmented?
    Any INSERT to a table could cause a page split and increase FREE_Space for your table. There are other causes as well, but this is the primary cause. DELETING sequential rows in a table will also increase FREE_Space. If you are NOT using innodb_file_per_table, this suggestion does NOT apply.  
    What should you do?
    If FREE_Space is less than 10% of DATA_Space you may consider this to be a tolerable relationship at this time and do nothing with OPTIMIZE.

    Determine file size from your OS perspective. Browse to your data folder and WRITE DOWN BEFORE size. If you are details oriented, you may find interesting for analysis purposes, 

    SHOW INDEX FROM tbl_name;
    to be compared with same SHOW INDEX FROM tbl_name; - AFTER OPTIMIZE. If file size is over 5 MB you may wish to schedule in your Maintenance window, OPTIMIZE of the table.
    OPTIMIZE TABLE (NO_WRITE_TO_BINLOG) tbl_name;
    Search in dev refman 5.7 13.7.2.4 for OPTIMIZE option details.
    The larger the file, the longer it will take and your table will be LOCKED. After completion, determine size of the file, WRITE DOWN AFTER size in your log of maintenance.
    SHOW INDEX FROM tbl_name; if you hope to compare them as a BEFORE/AFTER.

    Attach your text results and email to mydatalinks@mysqlservertuning.com for complimentary suggestions returned by email. 

    find-redundant-indexes-sql   < click to add to cart - then Checkout to complete 
    Quickly identify space/CPU time consuming indexes you should consider removing.  See documentation within the script, please - before taking action.  
    Added Jun 30, 2018

    Attach your text results and email to mydatalinks@mysqlservertuning.com for complimentary suggestions returned by email. 

    globalstatusage10sec.sql   < click to add to cart - then Checkout to complete 
    Determine resources used/freed for your MySQL instance for sleep seconds duration you manage in the script. Only reports items that have changed from beginning to end of sleep duration. Remember some GLOBAL STATUS counters roll over at 4,2nn,nnn,nnn back to 0 and continue counting. Specifically, Innodb_buffer_pool_read_requests at v 5.6.17 had this attribute. Later versions may or may not have this roll back to 0 attribute.

    globalstatusage10sec-wsum.sql   < click to add to cart - then Checkout to complete 
    Determine resources used/freed for your MySQL instance for sleep seconds duration you manage in the script. Only reports items that have changed from beginning to end of sleep duration. Sums the entire content of SHOW GLOBAL STATUS results, beginning and end with uptime visible and date/time.
    Remember some GLOBAL STATUS counters roll over at 4,2nn,nnn,nnn back to 0 and continue counting. Specifically, Innodb_buffer_pool_read_requests at v 5.6.17 had this attribute. Later versions may or may not have this roll back to 0 attribute.

    Innodb-data-GB-in-use.sql    < click to add to cart - then Checkout to complete 
    Quickly determine GB of data and indexes available in innodb buffer pool memory at this moment. Source of data is from Innodb_buffer_pool_pages_data from GLOBAL STATUS information.  Added July 15, 2018