Specify Azure SQL Server Connection Settings

Perform the following steps to configure Azure SQL Server as a Source in Hevo:

1. Click PIPELINES in the Navigation Bar.

2. Click + CREATE PIPELINE in the Pipelines List View.

3. On the Select Source Type page, select Azure SQL Server.

4. On the Configure your Azure SQL Server Source page, specify the following:

   

   • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.

   • Database Host: The Azure SQL Server host’s IP address or DNS.

     The following table lists a few examples of SQL Server hosts:

     Variant	Host
     Amazon RDS SQL Server	ms-sql-server-1.xxxxx.rds.amazonaws.com
     Azure SQL Server	mssql.database.windows.net
     Generic SQL Server	10.123.10.001 or mssql.westeros.inc
     Google Cloud SQL Server	35.220.150.0

     Note: For URL-based hostnames, exclude the http:// or https:// part. For example, if the hostname URL is https://mssql.database.windows.net, enter mssql.database.windows.net.

   • Database Port: The port on which your SQL Server is listening for connections. Default value: 1433.

   • Database User: The read-only user who has the permissions to read tables in your database.

   • Database Password: The password for the read-only user.

   • Select an Ingestion Mode: The desired mode by which you want to ingest data from the Source. You can expand this section by clicking SEE MORE to view the list of ingestion modes to choose from. Default value: Change Tracking. The available ingestion modes are Change Tracking, Table, and Custom SQL.

     

     Depending on the ingestion mode you select, you must configure the objects to be replicated. Refer to section, Object and Query Mode Settings for the steps to do this.

     Note: For Custom SQL ingestion mode, all Events loaded to the Destination are billable.

   • Database Name: The database that you wish to replicate.

   • Schema Name: The schema that holds the tables to be replicated. Default value: dbo.

     Note: When you replicate tables from a schema other than dbo, the schema name is prefixed to the table name and displayed as schemaname.tablename in the Objects list of the Pipeline Detailed View. The corresponding Destination table is created as destinationprefix_schemaname_tablename.

   • Connect Through SSH: Enable this option to connect to Hevo using an SSH tunnel, instead of directly connecting your SQL Server database host to Hevo. This provides an additional level of security to your database by not exposing your SQL Server setup to the public. Read Connecting Through SSH.

     If this option is disabled, you must whitelist Hevo’s IP addresses. Refer to the content for your SQL Server variant for steps to do this.

   • Advanced Settings:

     • Include New Tables in the Pipeline: Applicable for all ingestion modes except Custom SQL.

       If enabled, Hevo automatically ingests data from tables created in the Source after the Pipeline has been built. These may include completely new tables or previously deleted tables that have been re-created in the Source. All data for these tables is ingested using database logs, making it incremental and therefore billable.

       If disabled, new and re-created tables are not ingested automatically. They are added in SKIPPED state in the objects list, on the Pipeline Overview page. You can update their status to INCLUDED to ingest data.

       You can change this setting later.

     • Load Historical Data: Applicable for Pipelines with Logical Replication and Table mode. If this option is enabled, the entire table data is fetched during the first run of the Pipeline. If disabled, Hevo loads only the data that was written in your database after the Pipeline was created.

5. Click TEST CONNECTION. This button is enabled once you specify all the mandatory fields. Hevo’s underlying connectivity checker validates the connection settings you provide.

6. Click TEST & CONTINUE to proceed for setting up the Destination. This button is enabled once you specify all the mandatory fields.

Object and Query Mode Settings

Once you have specified the Source connection settings in Step 6 above, do one of the following:

• For Pipelines configured with the Change Tracking ingestion mode:

  1. On the Select Objects page, select the objects you want to replicate.

  2. Click CONTINUE. This button is enabled once you select at least one object for which Change Tracking is enabled.

     

     Note:

     • Each object represents a table in your database.

     • You must enable Change Tracking for the objects you want to ingest data from. If disabled, Hevo adds these objects to your Pipeline in the SKIPPED state.

     • For customers signing up after Release 2.19, Hevo automatically uses the Unique Incrementing Append Only (UIAO) query mode for the objects that contain a unique column. For the others, it ingests data using the Full Load query mode.

• For Pipelines configured with the Table ingestion mode:

  1. On the Select Objects page, select the objects you want to replicate and click CONTINUE.

     

     Note: Each object represents a table in your database.

  2. On the Configure Objects page, specify the query mode you want to use for each selected object.

     

  3. Click CONTINUE.

• For Pipelines configured with the Custom SQL ingestion mode:

  1. On the Provide Query Settings page, enter the custom SQL query to fetch data from the Source.

  2. In the Query Mode drop-down, select the query mode, and click CONTINUE.

     

Data Replication

Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.

• Historical Data: In the first run of the Pipeline, Hevo ingests all available data for the selected objects from your Source database.
• Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency.

Error 1003 - Authentication error

Error 1005 - Connection timeout

Error 1006 - Insufficient access

Error 1011 - Access denied