10 Replies Latest reply on Apr 7, 2020 9:58 AM by Giancarlo Corgnati

    Checking and Monitoring Remedy Database Size and Records

    Adam Lawson
      Share This:

      One of the biggest questions you'll have when setting up a new Remedy environment is "How big will our Database get"?  This will drive so many different changes to your overall architecture.  Even well established organizations that have used Remedy for years will have questions like "where is all of my data at?" this can drive decisions like how you want to set up archiving policies, disk configurations, and other information.


      Now I know there are a lot of database tools out there by both Oracle and Microsoft, but what happens when you need to look at this data and your DBA is on vacation and you don't have direct access?  Or if you just want a nice quick and easy GUI tool to look at this?  That's where our friends over at Remedy Legacy come in with their "DB Size" utility.  See below:


      DB Size – A Programming Legacy


      It is a client to AR System Server and it has the ability to provide you with a lot of helpful information on the number of records as well as the size (in bytes) that your database is consuming, while focusing on the EXACT tables the data lives on.  See below for steps on how to use it:


      Prerequisite: Configure the JAVA_HOME system variable.


      Steps to use:


      1. Download the utility from Remedy Legacy's website.
      2. Unzip it in a known location.

      3. Open the folder.
      4. CTRL+Shift+Right Click on any white space and choose "Open command Window here"

      5. Run the following command: "Java -jar APLDBSize.jar"

      6. This will open the APL DB Size Utility.  Enter your Server Name (AR System Server name), a Username and Password (User needs admin privileges) and the port number (for AR System Server).

      7. Then click the "Connect/Refresh" button.
      8. The results are now displayed in a table and you are able to sort and view them live.

      Notice that this breaks the results down into data, history records, attachment's.  It lets you know the number of records along with how much storage space it is taking up on the DB Server.


      As mentioned before, this can be valuable information to determine the growth of your database, the need for a archiving policy and where it is needed, as well as anything else you can imagine.


      Note: This only work with Java 8 SE currently.  Versions beyond Java 9 SE are not supported.