SQL Server as Target

Fivetran Local Data Processing supports integrating changes into SQL Server database. This section describes the configuration requirements for integrating changes (using and ) into SQL Server location. For the list of supported SQL Server versions, into which Local Data Processing can integrate changes, see in .

Local Data Processing uses the following interfaces to write data into an SQL Server location:

SQL Server ODBC driver, used to perform and .
SQL Server BCP interface, used for copying data into database tables during and .

Grants for Integrate and Refresh

This section lists the grants/permissions required for integrating changes into SQL Server database.

For simplicity, we have categorized the required permissions into the following two models:

DbOwner
In this permission model, the Local Data Processing database User must be made a database owner (db_owner role). Normally, the database objects that Local Data Processing sometimes creates will be part of the dbo schema as the replicated tables.
Alternatively, these Local Data Processing database objects can be put in a special database schema so that they are not visible to other users. For this, execute the following SQL commands:
```
create schema schemaname;

grant control on schema::schemaname to username;

alter user username with default_schema=schemaname;
content_copy
```
Minimal
In this permission model, the Local Data Processing database User does not need to be a database owner. The following SQL commands are needed so that Local Data Processing 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;
content_copy
```
If action is defined with parameter , then create procedure privilege is also needed.
```
grant create procedure to username;
content_copy
```
This permission model cannot be used if action is defined with parameter to change tables with a different owner.