Transaction journaling is required when running a mirror server in an installation. However, there may be scenarios when it must be stopped. A couple of example cases are: 

• The existing journal file gets inadvertently lost or deleted
• You no longer want to journal transactions for some reason
• You have taken a copy of a production database for a test environment and do not require journaling there
• In the unlikely event that the database becomes corrupt and you need to restore to a back-up database

This article describes how to stop transaction journaling. It can be done using the swDatabaseManager tool, or via a command line. Once stopped, if you wish to start journaling again (e.g., for the first 2 cases listed above), you will need to create a new journal file for the database.

• Using the swDatabaseManager
• Using a Command Line

Prerequisites

• Server and database compatible version of swDatabaseManager.exe tool
• If running against an SQLite database, the SystemWeaver server must be stopped, i.e., you must have sole access to the database when removing journaling
• The database has journaling activated, i.e., there is an existing .swjournal file associated with the database

Using the swDatabaseManager

1. As noted in the prerequisites, the SystemWeaver server application should be stopped if running a sqlite database. 
2. Open the swDatabaseManager.
3. Select the database Type and Select database.
4. On the Database tab, click the Display Info button to confirm that tool version is compatible with the database version. 
5. On the Mirroring tab, click Clear transaction info (Journaling).
   
   

The log window will indicate when the operation has completed. 

Using a Command Line

It is also possible to clear journaling via a command line. Remember that the SystemWeaver Server must be stopped to clear transaction information.

echo Clearing transaction info...
swDatabaseManager clearTransactionInfo type="SQLite" name="D:\backup.sqlite"
echo Done
pause