Configure 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).

   

2. Open SQL Server Management Studio.

   

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.

   

4. Create the FileAudit database:

   • In the Database name field, enter e.g. FileAudit.

   • Click OK.

   

   

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.

      

      

   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 Guide

   The FileAudit tables should be automatically created in the database and new events be inserted just after the first connection.

• 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.