All SQL Server transactions are logged to the Transaction Log file. The Transaction Log contains an audit trail by default and can grow to be quite large. To conserve disk space consider doing one of the following:
Use a truncated Transaction Log by default.
Use a CIMPLICITY maintenance action truncate the Transaction Log periodically.
Truncate the Log as a System Default
Open the SQL Enterprise Manager in the Microsoft SQL Manager program group.
From the Manage menu, select Databases. The Manage Databases dialog opens.
In the Manage Databases dialog, double click on the database used by the CIMPLICITY Database Logger. The Edit Database dialog opens.
In the Edit Database dialog, select the Options tab.
Select the Truncate Log on Checkpoint option.
Close the Manage Databases dialog.
Result: The change takes place the next time the SQL Server is restarted.
Truncate the Log as a CIMPLICITY Maintenance Action
Open the Database Logger in the CIMPLICITY program group.
Select a table from the list of tables.
Open the Table Properties dialog for the table.
Select the Maintenance Actions tab.
In the Command Action field, enter:
dump transaction DATABASENAME with no_log
This command will dump the Transaction Log without saving the log.
If you want to save the log to a file, see your SQL Server documentation on how to do this.
Select the Maintenance Events page.
Configure the event that will trigger the action.
This change takes place the next time you update the project's configuration and then restart the project.
It is recommended truncating the log as a system default.
To set truncate the log as a system default:
Open the SQL Enterprise Manager.
Select the database you are logging to.
Right-click on the database.
Select Properties from the popup menu.
Select the Options tab.
Make sure that Truncate Log On Checkpoint is checked.
Database management for SQL Server.