dotConnect Universal Connection Strings

Connection strings are key to configuring and managing dotConnect Universal connections to SQL Server, Oracle, MySQL, PostgreSQL, SQLite, and other data sources. This article explores practical ways and examples for building effective dotConnect Universal connection strings.

SQL Server provider connection strings

To connect to a SQL Server database using dotConnect Universal, you need to create a UniConnection object with a connection string. For example, the connection string can include basic parameters such as Provider, Server, User ID, Password, Database, and LicenseKey, as shown below.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=SQL Server;" +
    "Server=127.0.0.1;" +
    "User ID=TestUser;" +
    "Password=TestPassword;" +
    "Database=TestDb;" +
    "LicenseKey=**********");
...

However, dotConnect Universal supports numerous advanced connection string properties to fine-tune SQL Server database connections. These include settings for connection resilience, performance, optimization, security, or context management. The full list of such advanced properties is below.

Oracle provider connection strings

To establish a connection to an Oracle database using dotConnect Universal, you generally need to create a UniConnection object with a connection string. This string should contain basic properties like Provider, Direct, Server, Port, Sid, User Id, Password, and LicenseKey. Take a look at the example provided below.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=Oracle;" +
    "Direct=true;" +
    "Server=127.0.0.1;" +
    "Port=1521;" +
    "Sid=orcl;" +
    "User Id=TestUser;" +
    "Password=TestPassword;"
    "LicenseKey=**********");
...

Moreover, dotConnect Universal offers a wide range of advanced connection string properties to customize Oracle connection behavior beyond the basic connection parameters. These properties allow you to make settings such as performance, optimization, security, monitoring and other advanced configurations described in the following table.

Oracle Client provider connection strings

If you're connecting to Oracle Client using dotConnect Universal, your connection string typically includes basic properties like Provider, Data Source, User ID, Password, and LicenseKey, just like in the sample code that follows.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=OracleClient;" +
    "Data Source=127.0.0.1;" +
    "User ID=TestUser;" +
    "Password=TestPassword;"
    "LicenseKey=**********");
...

Still, the Oracle Client connection string can be extended with advanced properties to account for initialization, pooling, or security settings. Refer to the following table for details.

MySQL provider connection strings

Basic properties of a connection string you would use to connect to a MySQL database using dotConnect Universal would include the Provider, Server, User ID, Password, Database, and LicenseKey properties. An example of a connection object is provided below.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=MySQL;" +
    "Server=127.0.0.1;" +
    "User Id=TestUser;" +
    "Password=TestPassword;" +
    "Database=TestDb" +
    "LicenseKey=**********");
...

Yet, the connection string can just as well accommodate for more sophisticated settings of MySQL connection, such as initialization, performance and optimization, security, and other advanced configurations. Select the needed properties from the list below.

PostgreSQL provider connection strings

To connect to a PostgreSQL database using dotConnect Universal, you need to specify at least the basic properties, such as Provider, Host, Port, User Id, Password, Database, Initial Schema, and LicenseKey. Just like in the example below.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=PostgreSQL;" +
    "Host=127.0.0.1;" +
    "Port=5432;" +
    "User Id=TestUser;" +
    "Password=TestPassword" +
    "Database=TestDb" +
    "Initial Schema=Public" +
    "LicenseKey=**********");
...

If you would like to have more control over the PostgreSQL connection, then consider using advanced properties. The below list provides a comprehensive selection of properties to set up initialization, performance and optimization, security, and other connection parameters.

SQLite provider connection strings

For a connection to a SQLite database using dotConnect Universal, you need a connection string with basic properties such as Provider, Data Source, FailIfMissing, and LicenseKey. The below sample code shows how the connection string is formed.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=SQLite;" +
    "Data Source=mydatabase.db;" +
    "FailIfMissing=False;" +
    "LicenseKey=**********");
...

On top of this basic structure, you can add any of the advanced connection string properties for SQLite. Below you can find a whole set of properties that will let you configure your connection in terms of initialization, performance and optimization, security, and other advanced parameters.

MS Access provider connection strings

You can use dotConnect Universal to connect to MS Access and work with its data. To do this, you need a connection string with the following basic properties: Provider, Data Source, User ID, Password, Database, and LicenseKey. Refer to the sample code below to see how this can be done.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=MS Access;" +
    "Data Source=127.0.0.1;" +
    "User ID=TestUser;" +
    "Password=TestPassword;" +
    "Database=TestDb;" +
    "LicenseKey=**********");
...

To tweak your connection to MS Access, you have a whole bunch of advanced properties available. You can set up initialization, performance and optimization, security, and other parameters. Review the following list and select what suits your needs.

OLE DB provider connection strings

Your basic connection string to establish a connection using the OLE DB provider and dotConnect Universal would include the Provider, Data Source, User Id, Password, Database, and LicenseKey properties. The following example showcases such a connection.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=OLE DB;" +
    "Data Source=127.0.0.1;" +
    "UserId=TestUser;" +
    "Password=TestPassword;" +
    "Database=TestDb;" +
    "LicenseKey=**********");
...

And if you want to optimize or refine the OLE DB connection, you can use any of the advanced properties you have at hand, for example security or pooling parameters. Below is the list of available advanced properties for a connection string.

ODBC provider connection strings

A connection string with basic properties is generally enough to establish a connection using the ODBC provider and dotConnect Universal. Such properties are Provider, Data Source, User Id, Password, Database, and LicenseKey. Below is an example of their usage.

using Devart.Data.Universal;
...
UniConnection connection = new UniConnection("" +
    "Provider=ODBC;" +
    "Data Source=127.0.0.1;" +
    "User Id=TestUser;" +
    "Password=TestPassword;" +
    "Database=TestDb;" +
    "LicenseKey=**********");
...

However, you can have slightly more control over the ODBC connection with the use of advanced properties. The following table describes the available ones.

Conclusion

dotConnect Universal connection strings are fundamental to enabling proper communication between .NET applications and database back-ends. This guide has demonstrated the capabilities of connection strings when you use dotConnect Universal that can ensure reliable and efficient database interactions.

With its flexibility and support for multiple database providers, dotConnect Universal simplifies complex integration tasks, empowering developers to build robust, high-performance applications. Explore the full potential of dotConnect Universal by downloading the free trial today and experience how it meets your database connectivity needs!