Database Tab
- Last Updated: March 17, 2026
- 3 minute read
- MOVEit Transfer
- Version 2026
- Version 2025
- Documentation
Database
Settings of the current database engine used by MOVEit Transfer.
- Type MySQL
Configuration panel
- Server: IP address or hostname and instance of the MySQL database server used by MOVEit Transfer. Typically MOVEit Transfer uses a local MySQL database, so the server will usually be localhost.
- Database Name: Name of the database used by MOVEit Transfer. This was configured during setup; do not change it.
MOVEit User panel
- Username: Username of the database user used by MOVEit Transfer to access the DMZ database. This was configured during setup and should normally not be changed.
- Password (and Confirm): Password of the above database user. This password was configured during the MOVEit Transfer setup and should normally not be changed.
MySQL Root User panel
- Username: Name of the database root user. This was configured during setup and should normally not be changed.
- Password (and Confirm): Root password that is used to access the MySQL database for MOVEit Transfer. This password was configured during setup and should normally not be changed.
- Type Microsoft SQL Server or SQL Azure
Figure 1. Database Tab (Azure SQL shown) 
- Server\Instance: IP address or hostname of the SQL Server database server being used by MOVEit Transfer. When using a local SQL Server instance, this will typically be localhost. Otherwise, it will typically be the address of a separate database server or database cluster.
- Database Name: Name of the database used by MOVEit Transfer. This was configured during setup and should not be changed.
- Username: Name of the database user used by MOVEit Transfer to access the DMZ database. This was configured during setup and should normally not be changed.
- Password (and Confirm): Password of the above database user. This password was configured during the MOVEit Transfer setup and should normally not be changed.
MS SQL Server Read-only Database Performance Option
When you use MS SQL Server as the database engine for MOVEit Transfer, you can use the MOVEit Transfer Config Utility to leverage a read-only database instance that SQL Server HA (High-availability) offers you for scaling the heaviest read operations. The MOVEit Transfer Config Utility provides a Use read-only option for reporting in the Database tab. When selected, the system uses the SQL Server HA read-only database for the following reporting functions.
- Viewing audit logs through web interface (as opposed to application calls to the audit logs)
- Generating a report (both standard and custom reports)
- Upload data graphs and reports
Manual Option: Redirecting Report Generation to a Different Read-Only Instance:
If your MS SQL Server implementation does not use the built-in high availability feature, you can still run report generation and other I/O or compute intensive queries in a way that does not add latency to the system.
You can manually adjust the database connection string to handle these queries:
- Create a duplicate instance that is read-only, and
- Adjust the Connection String for Read-Only Connections to point at this instance.
| Advanced Database Settings Button
|
Read-only Database Option
|
| Setting/Control | Description | |
|---|---|---|
| 1 | Advanced Settings button | Reveals connection strings |
| 2 | Use read-only option for reporting checkbox | Check this to add the Read Only name-value pair to your connection string. (Using this with SQL Server Always On HA, is best practice.) |
| 3 | Connection String for Read-Only Connections | It is best practice not to edit this. It is visible and accessible for site specific changes, but you should ensure you test changes to this string before you make them on a live production system. |

