Set production database

Change the database FileAudit uses for auditing without moving your existing records to it.

Published June 23, 2026

Before you begin

FileAudit ships with a default SQLite database. For production use, we recommend switching to a more robust database: see Database architecture Reference for the supported options.

⚠️ This guide changes the production database without transferring your existing data. If you want to move your current data to the new database, use Migrate to another database instead.

Before you start, make sure you have:

  • The connection details for the destination database (server, instance, and credentials, depending on the provider).

  • Network access to the destination database from the FileAudit service.

Set the production database

  1. On the main screen, click the Database & audit maintenance tile. On the Database manager tab, click Edit.

  2. Click the three dots (...) at the end of the Connection string field to open the Database connection window.

    Edit database

  3. Select your database connector (such as SQL Server, ODBC Wizard, OLEDB Wizard, or SQLite) and click OK. A window opens for you to enter the connection details for that connector.

    Edit database properties

  4. Fill in the connection details and confirm.

  5. Back in the Edit database connection dialog, the Connection string field updates and shows Success. Click Save.

Confirm the new database is active

FileAudit now records new events in the database you set. To confirm it is working:

  1. Generate an event on one of your audited files or folders (for example, open or modify a file).

  2. Display the events for that path. See Displaying the events Getting started.

  3. Check that the event appears in the results.

If the event shows up, FileAudit is auditing against the new database.