---
locale: "en"
updated_at: "2026-08-10T08:16:05.708Z"
canonical: "https://www.isdecisions.com/en/fileaudit/docs/guides/database/configure-sql-server-express"
---

# Configure SQL Express

Set up SQL Express to work with FileAudit

## Setup SQL Express

Before connecting FileAudit to your database hosted in SQL Express, you need to prepare access to that database. Follow the guide below to do so:

1. Download and install **SQL Server Management Tools** (SSMS).
  ![](https://a.storyblok.com/f/122374/536x111/8e70c8d644/1-install-sql-server.png)
2. Open **SQL Server Management Studio**.
  ![](https://a.storyblok.com/f/122374/264x223/caba1f1121/2-microsoft-sql-server-management.png)
3. At the logon window:
  - Enter the server name and instance (e.g. `SERVERNAME\SQLEXPRESS`).
  - Choose **SQL Server Authentication**.
  - Enter your credentials and click **Connect**.
  ![](https://a.storyblok.com/f/122374/473x309/6067739e76/3-sql-server.png)
4. **Create the FileAudit database**:
  - In the **Database name** field, enter e.g. `FileAudit`.
  - Click **OK**.
  ![](https://a.storyblok.com/f/122374/327x424/a2587391ef/4-new-database.png)
  ![](https://a.storyblok.com/f/122374/673x417/2914391d7c/5-database-name.png)
5. **Add the account that is going to access the database. **Depending on the type of authentication you want to use in FileAudit — Windows or SQL Authentication — you need to add a different account.
  1. For **SQL Authentication**: create a dedicated SQL account (recommended, instead of using `sa`):
    - In **Login name**, type e.g. `FileAuditAdmin`.
    - Select **SQL Server authentication** and assign a password.
    - Adjust password policies if required by your IT policy (enforce policy, expiration, force change at logon).
    - Optionally set a default database and language.
    ![](https://a.storyblok.com/f/122374/261x478/e880667e3f/6-new-login.png)
    ![](https://a.storyblok.com/f/122374/695x615/b61d634cec/7-user-mapping.png)
  2. For **Windows Authentication**: by default, the FileAudit service runs as the SYSTEM account. If SQL Server is installed locally, add `NT AUTHORITY\SYSTEM`. If SQL Server is on a remote server, add the machine account `DOMAIN\FILEAUDITSERVER$` instead (replace `DOMAIN` and `FILEAUDITSERVER` with the corresponding names).
6. **Assign database roles**:
  - In **User Mapping**, select the `FileAudit` database.
  - Assign roles: `db_datareader`, `db_datawriter`, `db_ddladmin`.
  - Click **OK** to validate.
7. Then configure the connection string in FileAudit like explained in [Set production Database](/fileaudit/docs/guides/database/set-production-database) Guide
  The FileAudit tables should be automatically created in the database and new events be inserted just after the first connection.

> **Remote access to SQL Server**
>
> If your SQL Server is not installed on the same server as the FileAudit service, you need to enable remote connections in the SQL Server properties.
> You also need to enable TCP/IP in SQL Server Configuration Manager.

## Best practices

- **Secure authentication**: avoid using the `sa` account for day-to-day operations. Create a dedicated SQL account for UserLock with the required roles only.
- **Plan for growth**: SQL Express has a 10 GB size limit. Monitor usage and consider migrating to a full SQL Server if your deployment grows.
- **Set up backups early**: configure regular SQL Server backups before moving into production.
- **Restrict access**: limit network access to the SQL Express instance with proper firewall and permissions.