Skip to main content

How to Create a Data Source Name in Windows Control Panel

You can create a Data Source Name (DSN) in the Windows Control Panel to allow applications to connect to a database. This task is performed by an Account User within the Windows Control Panel (WCP) and is dependent on the specific database products...

You can create a Data Source Name (DSN) in the Windows Control Panel to allow applications to connect to a database. This task is performed by an Account User within the Windows Control Panel (WCP) and is dependent on the specific database products supported by your Hostek plan.

Important: This feature is only available if your Hostek plan includes the specific database software (such as Microsoft SQL Server) required for your application.

Before you begin

You will need:

  • Access to the Windows Control Panel (WPC)

  • The connection details for your database (server address, port, and database name)

  • Administrative permissions for the local Windows environment

Create a Data Source Name (DSN)

  1. Log in to the Windows Control Panel.

  2. Navigate to Tools > Data Sources (ODBC).

  3. Select the appropriate driver for your database (e.g., SQL Server or ODBC Driver for SQL Server).

  4. Click Add to create a new DSN.

  5. Enter a unique name for the DSN.

  6. Enter the server address and port (if applicable) in the server fields.

  7. Select the appropriate authentication method and enter the credentials.

  8. Select the specific database from the list or enter the database name.

  9. Click Finish or OK to save the configuration.

Confirm the result

  • The DSN will appear in the list of available Data Sources in the Windows Control Panel.

  • Your application can now select this DSN to establish a connection to the database.

Limitations

The availability of specific ODBC drivers and the ability to connect to certain database types depend on the specific products and licenses included in your Hostek plan. This procedure does not include the configuration of the database itself, only the creation of the local connection name.

Did this answer your question?