---
locale: "en"
updated_at: "2026-07-13T08:37:01.823Z"
canonical: "https://www.isdecisions.com/en/fileaudit/docs/guides/database/set-production-database"
---

# Set production database

Point FileAudit at a different production database without transferring data.

## Before you begin

FileAudit ships with a default SQLite database. For production use, we recommend switching to a more robust database: see [Database architecture](/fileaudit/docs/reference/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](/fileaudit/docs/guides/database/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](https://a.storyblok.com/f/122374/1020x654/c9f97c0a74/edit-database-connection.png)
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](https://a.storyblok.com/f/122374/1143x610/30570afe81/edit-database-properties.png)
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](/fileaudit/docs/getting-started/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.