Azure SQL Database as Target
Fivetran HVR supports integrating changes into Azure SQL Database. This section describes the configuration requirements for integrating changes (using Integrate and Refresh) into Azure SQL Database location.
HVR uses the following interfaces to write data into an Azure SQL Database location:
- SQL Server ODBC driver, used to perform Continuous Integrate and Row-wise Refresh.
- SQL Server BCP interface, used for copying data into database tables during Burst Integrate and Bulk Refresh.
When Refreshing Data with option Only Create Target Tables that are Missing in Azure SQL Database, option No Indexes should not be defined because Azure does not support tables without Clustered Indexes.
Grants for Integrate and Refresh
This section lists the grants/permissions required for integrating changes into Azure SQL Database.
For simplicity, we have categorized the required permissions into the following two models:
DbOwner
In this permission model, the HVR database User must be made a database owner (db_owner role). Normally, the database objects that HVR sometimes creates will be part of the dbo schema as the replicated tables.
Alternatively, these HVR database objects can be put in a special database schema so that they are not visible to other users. Following are the SQL commands for this alternate method:create schema schemaname; grant control on schema::schemaname to username; alter user username with default_schema=schemaname;
Minimal
In this permission model, the HVR database User does not need to be a database owner. The following SQL commands are needed so that HVR can create its own tables:grant create table to username; create schema schemaname; grant control on schema::schemaname to username; alter user username with default_schema=schemaname;
This permission model cannot be used if action TableProperties is defined with parameter Schema to change tables with a different owner.