The information in this FAQ applies to the following:

• ProHelp® EPM, Releases 6.2.0, 6.1.0, 6.0.0


• ProHelp® EPM, Releases 5.2.2, 5.2.1, 5.2.0, 5.1.0, 5.0.0

The Microsoft SQL Server transaction log records all database transactions (e.g., edits). It would be used to help restore your system in the event of a system crash.

Your database administrator should regularly perform Database Consistency Checks (DBCCs) and backup the database. If this is performed routinely, the transaction log will not fill up.

If the necessary database backups have not been performed, the transaction log may fill up. It will then be necessary to manually truncate the transaction log. To do this, follow these steps:

• Start the Microsoft SQL Server Enterprise Manager.


• Select the Tools menu and press SQL Query Tool.


• In the DB picklist, select the MATTEC_PROHELP database.


• Click the Load SQL Script icon and load the script C:\Program Files\Mattec\Prohelp\bin\util\EPMFULLLOGFIX.SQL.


• Click the Execute Query icon (green arrow).

If the message Stored procedure ‘DB_NAME’ not found is displayed, then your EPMFULLLOGFIX.SQL file hasn’t been configured properly. The value for DB_NAME should be changed to the name of your system’s database. Contact the Mattec Customer Service Department for additional information.

This script will perform the necessary Database Consistency Checks (DBCCs) then truncate the Transaction Log. Your system should now perform properly. However, it is a good idea to start backing up the database on a regular basis.