Dr. Livingstone, I Presume WELDWISE 2400 - Manual (Page 150)

11-4
0614-INS-400 Rev. D
Recommended maintenance
Refer to Database Management section in Chapter 6, the WMS reference Guide, for more information
about the database operations referenced in this document.
It is likely that a weld monitor recording welds made by a transfer line robot will gather significantly
more weld data than a system recording welds from a manually fed pedestal welder. For a typical
system, performing database maintenance once a week is a “suggested” and conservative starting
point.
The following steps should be performed in order, to “clean out” and minimize the size of the
databases. If weld data is being archived, it should be archived prior to performing these steps:
1) “Delete All Welds” - It is recommended that weld data be deleted so that the welddata.mdb
database is kept to less than 600Mbytes in size. This will make it easier for those who wish to
make a copy of the data prior to deleting weld data. A file size of 600Mbytes is still
manageable when copying data across the company network, querying the data, and archiving
the database files to a CD-R.
2) “Delete System Log” – The System Log records system events such as starting up, shutting
down, errors on the network, general diagnostic events, certain configuration events, database
upgrades, etc. Although this log does not fill up quickly, it is recommended that the log entries
be deleted any time weld data is deleted.
3) “Compact Database” – When information is deleted from a database, database records are
only ‘marked’ for deletion but still take up space in the database. For example, deleting the
system log does not make the livco.mdb file any smaller. Even if the system log were deleted
every day, livco.mdb would continue to grow. To recover this space and reduce the size of the
database file, the Compact Database operation should be performed periodically.