Location Connection for Azure SQL Database
This section describes the connection details required for creating Azure SQL Database location in Fivetran HVR. For information about the pre-requisites, access privileges, and other configuration requirements for creating Azure SQL Database location, see Azure SQL Database Requirements.
If the managed secrets feature is enabled, option USE TOKEN INSTEAD is displayed in the fields designated for entering secrets.
| Field | Description | Equivalent Location Property |
|---|---|---|
| SERVER | Fully qualified domain name (FQDN) of the Azure SQL Database. Example: cbiz2nhmpv.database.windows.net | SqlServer_Server |
| DATABASE | Name of the database in Azure SQL Database. Example: mytestdb | Database_Name |
| AUTHENTICATION METHOD | Authentication method for connecting HVR to Azure SQL database. Available options are:
| SqlServer_Authentication_Method |
| OAUTH2 ENDPOINT | URL used for obtaining the bearer token with credential token. Ensure that you are using the OAuth 2.0 endpoint. The URL path should include v2.0. The format for the endpoint URL is | Azure_OAuth2_Endpoint |
| CLIENT ID | Client ID used to obtain Microsoft Entra ID (formerly Azure Active Directory) access token. This field is available only if the AUTHENTICATION METHOD is set to Access Token. | Azure_OAuth2_Client_Id |
| CLIENT SECRET KEY | Secret key of the CLIENT ID. This field is available only if the AUTHENTICATION METHOD is set to Access Token. | Azure_OAuth2_Client_Secret |
| USER | User name and host name of the Azure SQL Database server. The format to be used is username@hostname. Example: hvruser@cbiz2nhmpv This field is available only if the AUTHENTICATION METHOD is set to User and Password or Microsoft Entra ID. | Database_User |
| PASSWORD | Password for the USER. This field is available only if the AUTHENTICATION METHOD is set to User and Password or Microsoft Entra ID. | Database_Password |
Advanced Settings
| Field | Description | Equivalent Location Property |
|---|---|---|
| LINUX / UNIX ODBC DRIVER MANAGER LIBRARY PATH | Directory path where the ODBC Driver Manager Library is installed. This field is applicable only for Linux/Unix operating system. For a default installation, the ODBC Driver Manager Library is available at /usr/lib64 and does not need to be specified. However, when UnixODBC is installed in for example /opt/unixodbc the value for this field would be /opt/unixodbc/lib. | ODBC_DM_Lib_Path |
| ODBCSYSINI | Directory path where the odbc.ini and odbcinst.ini files are located. This field is applicable only for Linux/Unix operating system. For a default installation, these files are available at /etc directory and do not need to be specified using this field. However, when UnixODBC is installed in for example /opt/unixodbc the value for this field would be /opt/unixodbc/etc. The odbcinst.ini file should contain information about the Snowflake ODBC Driver under the heading [ODBC Driverversionfor SQL Server]. | ODBC_Sysini |
| ODBC DRIVER | Name of the user defined (installed) ODBC driver used for connecting HVR to the Azure SQL Database. | ODBC_Driver |
| SQL Server Native Replicator Connection | If selected, disables the firing of database triggers, foreign key constraints and check constraints during integration if those objects were selected with not for replication. This is done by connecting to the database with the SQL Server replication connection capability. When this field is selected, the database connection string format in SERVER must be server_name,port_number, the other two formats of the connection string are not supported. This port_number must be configured in the Network Configuration section of the SQL Server Configuration Manager.
| SqlServer_Native_Replicator_Connection |