Web Tracks
    Help and Documentation
 Getting Started
    Getting Started with Web Tracks
    System Requirements
    Application Settings
    Configure Email Settings
    Customizing Fields & Forms
    License & Registration
    Dashboard Controls
    Database Maintenance
    Importing Users
    Manage Attachments
    Permissions & Access Levels
    Upsizing to SQL Server
    Working with Users
 General Information
    Compare Web Tracks Editions 
    Navigating Web Tracks
    Working with Graphs
    Working with Reports
    Working with File Attachments
    Asset Tags and Web Tracks
    Auditing Computers
    Working with Computers
    Working with Documentation
    Working with Peripherals
    Working with Software Assets
 Windows Applications
    Web Tracks Audit
    Web Tracks Database Updater
    Web Tracks Windows Service
    Web Tracks Report Designer
    Working with Purchase Orders
 Service Desk
    Working with Service Desk Tickets
    Working with the Knowledge Base
 Trouble Shooting
    RPC Errors when Auditing

Home > Administrative > Database Maintenance

Database Maintenance

The Database Maintenance form requires Administrative privileges to access.

This form is provided to maintain a manageable database. After using Web Tracks for some time, you may notice that some of the forms take longer to load. This is most likely caused by an increased size in your database.  You can reduce the size of your database by pruning old records.

Pruning Tables

Delete Disposed Equipment Records older than - When you dispose of computer or peripherals, the entire record is not actually deleted from the database. For tracking purposes, the records are moved to the Disposed table. This table is only accessed from the reporting module.  If you wish to delete records from this table, you must do so from this form.

Delete Closed Service Desk Tickets older than - If your service desk is highly used, over time this table will grow very large. After several years, the information in your old tickets becomes less valuable and you may want to prune some records to reduce the size of this table.

Delete Closed Purchase Orders older than - If your purchase order system is highly used, over time this table can also become very large. You most likely would only need to track these purchases for three to five years. After which, you may want to prune some of these records.

Reset Grid Columns for user - You may never need to use this option. The list column settings for Web Tracks Licensed Users are stored in your database. If for some reason they were to get corrupted, select their User ID from the drop down list and then click the Execute command. The next time the user logs in, his list column settings would be rebuilt.

Fix Database Referential Integrity Discrepancies

Web Tracks enforces referential integrity between your tables. For example, if a user ID was deleted from the database, the computer allocated to the user ID would become un-allocated because Web Tracks would set the allocation field (compUserID) to a Null value. However, if for some reason, another user was editing this computer record at the same time the user ID was deleted, the form would still show that the computer is allocated to this user. If the user who opened the computer record canceled his own update, there wouldn't be any discrepancies. However, if he saves the record, the computer would still be allocated to the deleted user (assuming he didn't change this part of the record). The odds of this happening are fairly minimal. However, just to be safe, Web Tracks includes this feature as a way to detect and fix these discrepancies.

Web Tracks will warn you about the number of records the query would delete. You will have the option of canceling the update query if you change your mind. Web Tracks fixes the discrepancies by setting the mis-matched values to null. If desired, you may choose to cancel the automated fix to investigate and/or manually fix the records in question.