# Microsoft Azure SQL Database (v1)

Information note **Microsoft Azure SQL Database extraction is supported by Stitch**   
This integration is powered by [Singer's](https://www.singer.io/) Microsoft Azure SQL Database tap and certified by Stitch. [Check out and contribute to the repo on GitHub](https://github.com/singer-io/tap-mssql).  
  
For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport).

## Microsoft Azure SQL Database feature snapshot

A high-level look at Stitch's Microsoft Azure SQL Database (v1) integration, including release status, useful links, and the features supported in Stitch.

| **STITCH** |  |  |  |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on July 12, 2019 | **Supported by**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) |
| **Stitch plan**<br><br>the Info icon<br><br>The type of Stitch plan required to use the integration. | Standard | **Supported versions**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. |  |
| **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**<br><br>the Info icon<br><br>Indicates if the integration is available as a source in Stitch Connect. | the Success icon<br><br>This version of the integration is available via the API.<br><br><br>Available | **Singer GitHub repository** | [singer-io/tap-mssql](https://github.com/singer-io/tap-mssql) |
| **CONNECTION METHODS** |  |  |  |
| **SSH connections**<br><br>the Info icon<br><br>Indicates if SSH tunnels are supported for connecting this database to Stitch. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **SSL connections**<br><br>the Info icon<br><br>Indicates if SSL connections are supported for connecting this database to Stitch. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **REPLICATION SETTINGS** |  |  |  |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **Table-level reset**<br><br>the Info icon<br><br>Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**<br><br>the Info icon<br><br>Indicates if Replication Methods can be defined by you for tables in the integration. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **REPLICATION METHODS** |  |  |  |
| **[Log-based Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental)**<br><br>the Info icon<br><br>Log-based Incremental Replication is a replication method in which Stitch identifies modifications to records - including inserts, updates, and deletes - using a database's binary log files. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Key-based Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental)**<br><br>the Info icon<br><br>Key-based Incremental Replication is a replication method in which Stitch identifies new and updated data using a column called a Replication Key. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **[Full Table Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/full-table)**<br><br>the Info icon<br><br>Full Table Replication is a replication method in which all rows in a table - including new, updated, and existing - are replicated during every replication job. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |  |  |
| **DATA SELECTION** |  |  |  |
| **Table selection**<br><br>the Info icon<br><br>The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Column selection**<br><br>the Info icon<br><br>The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **[View replication](https://help.qlik.com/en-US/stitch/replication/replicating-database-views)**<br><br>the Info icon<br><br>Indicates if Stitch supports replicating views from this database integration. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Select all**<br><br>the Info icon<br><br>Indicates if the integration supports selecting all available tables and columns. | the Warning 2 icon<br><br>Log-based Incremental Replication must be enabled and set as the default Replication Method to use the Select All feature.<br><br><br>Supported, with prerequisites |
| **TRANSPARENCY** |  |  |  |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**<br><br>the Info icon<br><br>Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**<br><br>the Info icon<br><br>Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |

## Connecting Microsoft Azure SQL Database

### Microsoft Azure SQL Database setup requirements

To set up Microsoft Azure SQL Database in Stitch, you need:

* **Privileges in Microsoft Azure SQL Database that allow you to create/manage users.** This is required to create the Stitch database user.

* **If using Log-based Incremental Replication**, you’ll need:

  * **The `ALTER DATABASE` privilege in Microsoft Azure SQL Database.** This is required to complete the setup for Log-based Incremental Replication.
  * **A Primary Key in the source table.** This is required to use logical replication.

### Step 1: Verify your Stitch account's data pipeline region

First, you’ll log into Stitch and verify the data pipeline region your account is using. Later in this guide, you’ll need to grant Stitch access by whitelisting our IP addresses.

The IP addresses you’ll whitelist depend on the [**Data pipeline region** your account is in](https://help.qlik.com/en-US/stitch/security/supported-data-pipeline-regions).

1. [Sign into your Stitch account](https://app.stitchdata.com/), if you haven’t already.

2. Click **User menu (your icon) &gt; Edit User Settings** and locate the **Data pipeline region** section to verify your account’s region.

3. Locate the list of IP addresses for your region:

   * [North America region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#north-america-ip-addresses)

   * [Europe region IP addresses](https://help.qlik.com/en-US/stitch/security/stitch-ip-addresses#europe-ip-addresses)

Keep this list handy - you’ll need it later.

### Step 2: Configure database connection settings

In this step, you’ll configure the database server to allow traffic from Stitch to access it. There are two ways to connect your database:

* **A direct connection** will work if your database is publicly accessible.
* **An SSH tunnel** is required if your database isn’t publicly accessible. This method uses a publicly accessible instance, or an SSH server, to act as an intermediary between Stitch and your database. The SSH server will forward traffic from Stitch through an encrypted tunnel to the private database.

Click the option you’re using below and follow the instructions.

I'm using an SSH tunnel to connect.

1. Follow the steps in the [Setting up an SSH Tunnel for a Microsoft Azure database guide](https://help.qlik.com/en-US/stitch/security/data-encryption/setting-up-ssh-tunnel-for-microsoft-azure) to set up an SSH tunnel for Microsoft Azure SQL Database.
2. Complete the steps in this guide after the SSH setup is complete.

#### I'm using a direct connection.

For the connection from Stitch to be successful, you’ll need to configure the firewall for your instance to allow access from IP addresses for your [Stitch data pipeline region](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#verify-stitch-account-region).

1. Sign into your [Microsoft Azure portal](https://azure.microsoft.com/en-us/account/).

2. Locate and open the database you want to connect to Stitch.

3. Click **Settings &gt; Connection security**.

4. For each of the IP addresses you retrieved in [Step 1](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#verify-stitch-account-region) for your Stitch data pipeline region, create a rule:

   * **Rule name**: Enter a name for the rule. For example: `Stitch<number>`
   * **Start IP**: Paste one of the Stitch data pipeline region IP addresses.
   * **End IP**: Paste the same IP address.

5. Click the three dots to the right of the **End IP** field to add the rule.

6. Repeat steps 4 and 5 until there is a rule for each IP address for your Stitch data pipeline region. Below is an example of what this might look like using Stitch’s North America IP addresses:

   ![IP address rules for Stitch's North America IP addresses in Microsoft Azure firewall settings](https://help.qlik.com/en-US/stitch/images/destinations/microsoft-azure-ip-addresses.png)IP address rules for Stitch's North America IP addresses in Microsoft Azure firewall settingsIP address rules for Stitch's North America IP addresses in Microsoft Azure firewall settings

   **Note**: You may also want to add your own IP address(es) to this list. This ensures that you’ll also be able to connect to the database as needed.

7. Click **Save**.

### Step 3: Enable Log-based Incremental Replication with Change Tracking

Information note **Note**: Skip this step if you’re not planning to use Log-based Incremental Replication. [Click to skip ahead](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#db-user).

While Log-based Incremental Replication is the most accurate and efficient method of replication, using this replication method may, at times, require manual intervention or impact the source database’s performance. Refer to the [Log-based Incremental Replication documentation](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) for more info.

You can also use one of Stitch’s other [Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods), which don’t require any database configuration. Replication Methods can be changed at any time.

* [Step 3.1: Verify database compatibility](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#verify-database-compatibility)

* [Step 3.2: Enable change tracking for the database](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#enable-database-change-tracking)

* [Step 3.3: Enable change tracking for tables](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#enable-table-change-tracking)

#### Step 3.1: Verify database compatibility

Information note **Note**: The `SELECT` from `sys.databases` and `ALTER DATABASE` privileges are required to complete this step.

In this step, you’ll verify the database’s [database’s compatibility level](https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level?view=sql-server-2017). This setting sets some database behaviors to be compatible with a specified version of SQL Server. To use Change Tracking, your database must have a compatibility level greater than `90`.

1. Log into your database:

   ```
   USE <database_name>
   GO
   ```

2. Run the following query to retrieve the database’s current compatibility level:

   ```
   SELECT compatibility_level
   FROM sys.databases WHERE name = '<database_name>';
   GO
   ```

   According to [Microsoft’s documentation](https://docs.microsoft.com/en-us/sql/relational-databases/track-changes/enable-and-disable-change-tracking-sql-server?view=sql-server-2017#enable-change-tracking-for-a-database), this value must be greater than `90` or the `CHANGETABLE` function (used to obtain change tracking info during replication) will return an error.

3. If the result is less than `90`, you’ll need to increase it to enable Change Tracking.

   **Note**: Before changing this setting, you should understand how doing so could impact your database. Refer to [Microsoft’s documentation](https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level?view=sql-server-2017) for more info.

   Use the following command to set the database compatibility level:

   ```
   ALTER DATABASE <database_name>
   SET COMPATIBILITY_LEVEL = 100;
   GO
   ```

#### Step 3.2: Enable change tracking for the database

Information note **Note**: You must have the `ALTER DATABASE` privilege to complete this step.

In this step, you’ll enable Change Tracking at the database level. Use the following command to enable Change Tracking, replacing `<database_name>` with the name of the database:

```
ALTER DATABASE <database_name>  
SET CHANGE_TRACKING = ON  
(CHANGE_RETENTION = 3 DAYS, AUTO_CLEANUP = ON)
```

This command also defines the `CHANGE_RETENTION` and `AUTO_CLEANUP` settings:

* `CHANGE_RETENTION` - This specifies the time period for which change tracking information is kept. Change tracking information older than the specified time period is periodically removed by Microsoft Azure SQL Database. Stitch recommends a **minimum** of `3 days`.

* `AUTO_CLEANUP` - This controls the cleanup task that removes old change tracking information. When `OFF`, the task will be disabled and old change tracking information will not be removed.

  Information note **Tip:** If you encounter an issue with a table, change `AUTO_CLEANUP` to `OFF` to disable cleanup tasks. This will ensure change tracking info is retained, allowing Stitch Support to more thoroughly investigate.

#### Step 3.3: Enable change tracking for tables

For every table you want to replicate using Log-based Incremental Replication, you will need to enable change tracking. When change tracking is enabled, change tracking information will be maintained for all rows in the table affected by a DML operation.

Run the following command to enable change tracking for a table:

```
ALTER TABLE <schema_name>.<table_name>  
ENABLE CHANGE_TRACKING  
WITH (TRACK_COLUMNS_UPDATED = ON)
```

Repeat this step for every table you want to replicate using Log-based Incremental Replication.

### Step 4: Create a Stitch database user

Next, you’ll create a dedicated database user for Stitch. This will ensure Stitch is visible in any logs or audits, and allow you to maintain your privilege hierarchy.

* Instructions
* Privileges list

Creating a user with `SELECT` privileges can either be done via a query or the Microsoft Azure SQL Database UI. In this section, we’ll walk you through using the query method.

Depending on your setup and the access you grant to the Stitch database user, you may need to create several Microsoft Azure SQL Database integrations to allow Stitch to replicate all your data. This is due to a Microsoft Azure SQL Database limitation on how access is granted to `sys.database` views.

* If the Stitch user has access to the master database and this database is then used for authentication, you can replicate all databases that the user has access to from a single Microsoft Azure SQL Database integration setup.

* If the database you’re replicating isn’t the master database, you’ll only be able to replicate schemas and tables within that database. This will require creating additional Microsoft Azure SQL Database integrations in Stitch.

Information note **Important**: This user’s language setting must be set to `us_english`. Issues with replication may arise if a different setting is used.

1. Create the Stitch database user, replacing `<database_name>` with the name of the database and `<password>` with a secure password:

   ```
   USE <database_name>
   CREATE LOGIN <stitch_login> WITH PASSWORD='<password>';
   CREATE USER <stitch_username> FOR LOGIN <stitch_login>;
   GO
   ```

2. Grant the Stitch user `SELECT` privileges by running this command for every table you want to replicate:

   ```
   GRANT SELECT ON <schema_name>.<table_name> TO <stitch_username>;
   GO
   ```

   Limiting access to only the tables you want to replicate ensures that the integration can complete discovery (a structure sync) in a timely manner. If you encounter issues in Stitch where tables aren’t displaying, try limiting the Stitch database user’s table access.

   **Note:** Column-level permissions are not supported for use with Log-based Incremental Replication. Restricting access to columns will cause replication issues.

Information note

**Important:** **Using Log-based Incremental Replication**

Additionally, if you want to use Log-based Incremental Replication, you’ll also need to grant the Stitch user `VIEW TRACKING CHANGES` privileges on the [tables where change tracking is enabled](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#enable-table-change-tracking):

```
GRANT VIEW CHANGE TRACKING ON <schema_name>.<table_name> TO <stitch_username>;
GO
```

For every table you want to replicate, you’ll need to run this command.

See the **Privileges list** tab for an explanation of why these permissions are required by Stitch.

In the table below are the database user privileges Stitch requires to connect to and replicate data from a Microsoft Azure SQL Database database.

| **Privilege name** | **Reason for requirement** |
| --- | --- |
| [SELECT](https://docs.microsoft.com/en-us/sql/t-sql/statements/grant-object-permissions-transact-sql?view=sql-server-2017) | Required to select rows from tables in a database. |
| [VIEW CHANGE TRACKING](https://docs.microsoft.com/en-us/sql/relational-databases/track-changes/manage-change-tracking-sql-server?view=sql-server-2017) | **Required to use Log-based Incremental Replication.** Required to obtain change tracking information from tables where change tracking is enabled. |

### Step 5: Connect Stitch

In this step, you’ll complete the setup by entering the database’s connection details and defining replication settings in Stitch.

* [Step 5.1: Define the database connection details](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#define-connection-details)

* [Step 5.2: Define the SSH connection details](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#ssh-connection-details)

* [Step 5.3: Define the SSL connection details](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#ssl-connection-details)

* [Step 5.4: Define Log-based Replication setting](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#define-log-based-replication-setting)

* [Step 5.5: Create a replication schedule](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#create-replication-schedule)

#### Step 5.1: Define the database connection details

1. If you aren’t signed into your Stitch account, [sign in now](https://app.stitchdata.com/).

2. On the Stitch Dashboard page, click the **Add Integration** button.

3. Locate and click the **Microsoft Azure SQL Database** icon.

4. Fill in the fields as follows:

   * **Integration Name**: Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

     For example, the name “Stitch Microsoft Azure SQL Database” would create a schema called `stitch_microsoft_azure_sql_database` in the destination. **Note:** The schema name cannot be changed after the integration is saved.

   * **Host (Endpoint)**: Enter the host address (endpoint) used by the Microsoft Azure SQL Database instance. This is usually a server endpoint like `<server-name>.database.windows.net`.

   * **Port**: Enter the port used by the Microsoft Azure SQL Database instance. The default is `1433`.

   * **Username**: Enter the Stitch Microsoft Azure SQL Database user’s username. We recommend copying and pasting the username Microsoft Azure SQL Database displays to you directly into this field. **Note**: Verify that the name includes `'@domain'` or you’ll run into connection issues.

   * **Password**: Enter the password for the Stitch Microsoft Azure SQL Database database user.

   * **\*\*: \*\*Optional:** Enter the name of the default database Stitch will connect to. Stitch will ‘find’ all databases you give the Stitch user access to - a default database is only used to test and complete the connection.

     **Note**: If this field is defined, Stitch will attempt to connect to only the database entered. If undefined, Stitch will attempt to connect to all of the databases the Stitch user has access to. To connect several specific databases, create an integration for each database you want to connect and define it in this field.

   * **Include Microsoft SQL Server schema names in destination tables**: Checking this setting will include schema names from the source database in the destination table name - for example: `<source_schema_name>__<table_name>`.

     Stitch loads all selected replicated tables to a single schema, preserving only the table name. If two tables canonicalize to the same name - even if they’re in different source databases or schemas - name collision errors can arise. Checking this setting can prevent these issues.

     **Note**: This setting can not be changed after the integration is saved. Additionally, this setting may create table names that exceed your destination’s limits. For more info, refer to the [Database Integration Table Name Collisions guide](https://help.qlik.com/en-US/stitch/troubleshooting/data-discrepancies/database-integration-table-name-collisions).

#### Step 5.2: Define the SSH connection details

Information note **Note**: Skip this step if you’re not using SSH to connect to Stitch.

If you’re using an SSH tunnel to connect your Microsoft Azure SQL Database database to Stitch, you’ll also need to define the SSH settings. Refer to the [Setting up an SSH Tunnel for a Microsoft Azure database guide](https://help.qlik.com/en-US/stitch/security/data-encryption/setting-up-ssh-tunnel-for-microsoft-azure) for assistance with completing these fields.

1. Click the **SSH Tunnel** checkbox.

2. Fill in the fields as follows:

   * **SSH Host**: Enter the public IP address or hostname of the server Stitch will SSH into.

   * **SSH Port**: Enter the SSH port on your server. (`22` by default)

   * **SSH User**: Enter the Stitch Linux (SSH) user’s username.

#### Step 5.3: Define the SSL connection details

Information note **Note**: Skip this step if you’re not using SSL to connect to Stitch.

Click the **Connect using SSL** checkbox if you’re using an SSL connection. **Note:** The database must support and allow SSL connections for this setting to work correctly.

#### Step 5.4: Define Log-based Replication setting

Information note **Note**: Skip this step if you’re not planning to use Log-based Incremental Replication. [Click to skip ahead](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#create-replication-schedule).

In the **Log-based Replication** section, you can set this as the integration’s default Replication Method.

When enabled, tables that are set to replicate will use [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) by default. If you don’t want a table to use Log-based Incremental Replication, you can change it in the Table Settings page for that table.

If this setting isn’t enabled, you’ll have to select a [Replication Method](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#sync-data) for each table you set to replicate.

#### Step 5.5: Create a replication schedule

Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.

In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Microsoft Azure SQL Database integrations support the following replication scheduling methods:

* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)

* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)

* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.

### Step 6: Select data to replicate

Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).

The last step is to select the tables and columns you want to replicate. [](https://help.qlik.com/en-US/stitch/integrations/databases/microsoft-azure/v1#schema)

**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.

* Selection options
* Individual tables and columns
* All tables and columns
* Database views

For Microsoft Azure SQL Database integrations, you can select:

1. **Individual tables and columns**

2. **All tables and columns** (except views)

3. **Database views**

Click the tabs to view instructions for each selection method.

1. In the Integration Details page, click the **Tables to Replicate** tab.

2. Locate a table you want to replicate.

3. Click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.

4. After you set a table to replicate, a page with the table’s columns will display. De-select columns if needed.

5. Next, you’ll define the table’s Replication Method. Click the **Table Settings** button.

6. In the **Table Settings** page:

   1. Define the table’s **Replication Method**.

   2. If using [Key-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental), select a [Replication Key](https://help.qlik.com/en-US/stitch/replication/replication-keys).

   3. When finished, click **Update Settings**.

7. Repeat this process for every table you want to replicate.

8. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

Information note

**Important:** Before using this feature, note that:

1. Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections.

2. Log-based Incremental Replication must be enabled and set as the default Replication Method to use the Select All feature.

Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.

1. Click into the integration from the Stitch Dashboard page.

2. Click the **Tables to Replicate** tab.

3. Navigate to the table level, selecting any databases and/or schemas that contain tables you want to replicate.

4. In the list of tables, click the box next to the **Table Names** column.

5. In the menu that displays, click **Track AllTables and Fields (Except Views)**:

   ![The Track AllTables and Fields (Except Views) menu in the Tables to Replicate tab](https://help.qlik.com/en-US/stitch/images/replication/select-all-tables-menu.png)The Track AllTables and Fields (Except Views) menu in the Tables to Replicate tabThe Track AllTables and Fields (Except Views) menu in the Tables to Replicate tab

6. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

Setting a database view to replicate is similar to selecting a table, with a few differences. Refer to the [Replicating Database Views guide](https://help.qlik.com/en-US/stitch/replication/replicating-database-views) for detailed instructions.

At a high level, you’ll need to complete the following to select a database view:

1. [Verify the database user’s permissions](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--verify-database-user-permissions)
2. [Select the view](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--select-view-in-stitch)
3. **Optional**: [Define the view’s Primary Key](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--define-view-primary-key)
4. [Define the view’s Replication Method](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--define-view-replication-method)
5. [Save the view’s settings](https://help.qlik.com/en-US/stitch/replication/replicating-database-views#step--save-view-settings)

### Initial and historical replication jobs

After you finish setting up Microsoft Azure SQL Database, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**

Information note

**Initial replication jobs with Anchor Scheduling**

If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.

#### Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.