Now click the Test button to establish a test connection to your data source.In the appeared dialog, specify the required connection settings and click OK.Find the DEVART_SQLSERVER section and click the Configure button: Run the iODBC utility of the required bitness.You can use it to test a connection with SQLSERVER server.
To activate the driver, perform the steps described in the Product Activation article.Īfter the driver is installed, DSN with the name DEVART_SQLSERVER is created.
If you have the activation key file, click the Load Activation Key button and browse to it.Copy the activation key from the registration email or your Customer Portal account and paste it into the Activation Key edit box. If you have an activation key, select the Activation Key option. If you have no activation key, you can select Trial and use the driver for evaluation purposes. In the License Information dialog box, you should select the license type and activate the product. Run the downloaded file and follow the instructions in the wizard.Īfter reading the license agreement, click Agree to proceed with the installation. Download the PKG file from the Devart website.
In case when using other ODBC driver managers, ODBC Driver for SQL Server will be installed, but it will require manual modification of configuration files of these managers. ODBC Driver for SQL Server is compatible with iODBC driver manager. ODBC driver manager is not distributed along with our driver and must be installed separately. Specify additional segments after the account locator.ODBC Driver for SQL Server works under control of an ODBC driver manager.
The account uses a different cloud provider, you need to If the account is in a different region or if Note that testodbc2 uses an account in the AWS US West (Oregon) region. This article provides commands for installing the ODBC driver from the bash shell. It also includes instructions for the optional command-line tools for SQL Server (bcp and sqlcmd) and the unixODBC development headers.
Testodbc2 uses the account locator xy12345 as the account identifier. This article explains how to install the Microsoft ODBC Driver for SQL Server on Linux. Testodbc1 uses an account identifier that uses anĪccount identifier that specifies the account myaccount in the organization The following example illustrates an odbc.ini file that configures two data sources that use different forms of an For details about the parameters that can be set for each DSN, see ODBC Configuration and Connection Parameters. Parameters are specified in the form of =. Any connection parameters you add to the DSN do not need to be specified in the ODBC connect string.Īny additional parameters, such as default role, database, and warehouse.
ĭirectory path and name of the driver file, in the form of Driver = /opt/snowflake/snowflakeodbc/lib/universal/libSnowflake.dylib.Ĭonnection parameters, such as server and uid (user login name). If you are creating the first DSNįor the driver, you must manually create the odbc.ini file and add the entry to the file.ĭSN name and driver name (Snowflake), in the form of =. If a user or system DSN has already been created for the driver, add the new entry to the odbc.ini file that already exists in the corresponding directory for the type of DSN you are creating. Creating a DSN by Adding an Entry in the odbc.ini File ¶