The ShipRush Database Manager is a tool provided on the installation of ShipRush. There are no icons created for it, but the importance of this tool for avoiding database issues and maximizing the speed and efficiency of your main ShipRush database cannot be understated.
Although the database manager has a number of other features, in this article we are going to focus on the Purge and the Repair/Index Rebuild features of the database manager. These two features are extremely important to understand, and need to be performed on a periodic basis but at least every 90 days. Doing so ensures the stability, speed and connectivity to the ShipRush database.
The ShipRushDBManger.exe program is located at C:\Program Files (x86)\Z-Firm LLC\ShipRush v11\ and must be executed from the machine where the database is located. It also must be run during periods of time when the administrator can stop the ShipRush service and no shipping is being done.
Once in the program, click on the DB Maintenance Tab. The features we will discuss are highlighted in yellow. The Backup is highlighted because it is always recommended to back up the database previous to performing any critical database functions. The second step is to Purge data, followed by Repair/Index and rebuild.
Step 1: Backing up the ShipRush Database
To back up the database, click the Backup Button. No other intervention is needed. Because the database manager automatically backups the database, it is a very good idea to note where the backup is being stored (highlighted in green), in case it is needed later.
Step 2: Purging data
Purging does exactly what it implies. It removes any locally stored shipment data prior to a defined date. Purging data is done primarily to improve the efficiency of the database. ShipRush updates often include table changes, and each record must be exported and re-imported on the update process. Without a proper purging process in place this could add a lot of extra time to an update.
Purging only eliminates this data from the local database. Because these shipments have been scanned by the carrier, the information for these shipments now resides with them.
To purge data, select a date to purge to (ShipRush suggests 90 days as a maximum). In the example below, all data will be purged previous to 5/1/2016. Once a date has been selected, click Purge.
The program will not warn you, or ask you to continue. Once you click Purge the program will automatically start purging data.
Step 3: Repair/Index and Rebuilding
After purging the data, you have the option to Repair/Index and Rebuild the database. It is suggested to include this with your Purging policy. Running this function not only re-indexes existing shipment data, but it also re-indexes all of the ShipRush tables that are not directly related to the shipments.
With a ShipRush file based database, indexes are stored as files. Files not only can become corrupt, they can also become fragmented on a hard drive. Rebuilding and re-Indexing ensures that you have these files in the optimum state for looking-up, retrieving, and storing data.
This function also works in conjunction with the checkbox “Auto Verify and re-run Repair if needed”. It is highly suggested to check this box. ShipRush actually does all three things in the button’s description. Checking this box ensures that any corrections made are verified and rebuilt if necessary.
Purging data is not only recommended, it is essential to the efficient use of ShipRush. The ShipRush database, by design, was never intended to be a shipping data repository. Retaining too many records opens the database to susceptibility to index and file fragmentation, as well as speed degradation. It also prolongs ShipRush updates.
Rebuilding data ensures the optimum efficiency in looking-up, retrieving and storing data.
Running these two functions at a maximum of 90 day intervals, will ensure that you are using ShipRush at its peak data capability.