SQL Server as Target

Data Source Solutions DSS supports integrating changes into SQL Server database. This section describes the configuration requirements for integrating changes (using Integrate and Refresh) into SQL Server location. For the list of supported SQL Server versions, into which DSS can integrate changes, see Integrate changes into location in Capabilities.

DSS uses the following interfaces to write data into an SQL Server location:

• Microsoft ODBC Driver for SQL Server, 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.

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 DSS database User must be made a database owner (db_owner role). Normally, the database objects that DSS sometimes creates will be part of the dbo schema as the replicated tables.
  Alternatively, these DSS 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 <em>schemaname</em>;
  
  grant control on schema::<em>schemaname</em> to <em>username</em>;
  
  alter user <em>username</em> with default_schema=<em>schemaname</em>;
  

• Minimal
  In this permission model, the DSS database User does not need to be a database owner. The following SQL commands are needed so that DSS can create its own tables:

  grant create table to <em>username</em>;
  
  create schema <em>schemaname</em>;
  
  grant control on schema::<em>schemaname </em>to <em>username</em>;
  
  alter user <em>username </em>with default_schema=<em>schemaname</em>;
  

This permission model cannot be used if action TableProperties is defined with parameter Schema to change tables with a different owner.