--- title: "Best practice: Test SQL database connectivity with test.udl file" slug: "best-practice-test-sql-database-connectivity-with-test-udl-file" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:02Z published: 2026-09-07T17:46:02Z canonical: "docs.trellix.com/best-practice-test-sql-database-connectivity-with-test-udl-file" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Best practice: Test SQL database connectivity with test.udl file For database connection issues, you can use the test.udl file to confirm the database credentials used to access the SQL database from the ePO - On-prem server. You must know the SQL database server name and database name on the server. Use the `https://<localhost>:8443/core/config-auth` URL to learn this information. If you are troubleshooting ePO - On-prem database connection problems, you might see this error in the orion.log file: `Login failed for user ''. The user is not associated with a trusted SQL Server connection` For details about product features, usage, and best practices, click ? or Help. 1. On the ePO - On-prem server, create a file named `test.udl`. 2. Double-click the file you created to display the Data Link Properties user interface. 3. Click the **Provider** tab, select **Microsoft OLE DB Provider for SQL Server** from the OLE DB Provider(s) list, then click **Next**. 4. On the Connection tab, configure this information: - **Select or enter a server name** — Type the server name, instance, and port using this format: `<servername>\<instancename>,<port>`. If no named database instance is used, use this format: `<servername>,<port>` - **Enter information to log on to the server** — Type the SQL database credentials. - **Select the database on the server** — Type the database name. 5. Click **Test Connection**. The Microsoft Data Link dialog box should display **Test connection succeeded**.