Learn more about Microsoft SQL Server Tables Export Integration.

This article describes how to use the data connector for Microsoft SQL Server, which allows you to directly import data from your Microsoft SQL Server to Treasure Data.

For sample workflows on how to import data from your Microsoft SQL Server, view Treasure Boxes.


  • Basic knowledge of Treasure Data

  • Basic knowledge of Microsoft SQL Server

  • A Microsoft SQL Server instance running remotely, for example on RDS.

Use the TD Console to Create Your Connection

You can use the TD Console to configure your connection.

Create a New Connection

When you configure a data connection, you provide authentication to access the integration. In Treasure Data, you configure the authentication and then specify the source information.

Go to Integrations Hub ->  Catalog and search and select Microsoft SQL Server.

The following dialog opens.

Provide the required credentials, including the host name, port, user name and password required to access Microsoft SQL Server.

If you add the option encrypt=true and your certificate can't be validated, you need to add the option trustServerCertificate=true to bypass the certificate validation.

Select Continue

Name your new Microsoft SQL Server Connection. Select New Source.

Transfer Your Microsoft SQL Server Data to Treasure Data

You created your authenticated connection, now you create the source connection.
Complete the details and select Next

If you want to specify the schema, select Use custom SELECT query as follows:


You’ll see a preview of your data. To make changes, select Advanced Settings otherwise, select Next.

Choose the Target Database and Table

Choose an existing or create a new database and table where you want to transfer data to:

Create new database and give your database a name. Complete similar steps for Create new table.

Select whether to append records to an existing table or replace your existing table.

If you want to set a different partition key seed rather than use the default key, you can specify one. 


In the Schedule tab, you can specify a one-time transfer, or you can schedule an automated recurring transfer. If you select Once now, select Start Transfer. If you select Repeat… specify your schedule options, then select Schedule Transfer.

Name your Source connector. You can just save the connector or select Create & Run.

Use Command-Line to Create Your Microsoft SQL Server Connection

You can use the CLI to configure your connection. 

Install ‘td’ command

Install the newest TD Toolbelt.

Create Seed Config File (seed.yml)

Prepare seed.yml with your Microsoft SQL Server access information:

  type: sqlserver
  host: sqlserver_host_name
  port: 1433
  user: test_user
  password: test_password
  database: test_database
  table: test_table
  mode: replace

This example will dump all records inside the table. You can have more detailed control with additional parameters.

For more details on available out modes, see the Appendix below.

Guess Fields (Generate load.yml)

Next use connector:guess. This command automatically reads the target data, and intelligently guesses the data format.

$ td connector:guess seed.yml -o load.yml

If you open up load.yml, you’ll see guessed file format definitions including, in some cases, file formats, encodings, column names, and types.

Optional: Preview data to be imported

You can preview data to be imported using the command td connector:preview.

$ td connector:preview load.yml
| id:long | name:string  | description:string               | price:long | created_at:timestamp      |
| 1       | "item name1" | "26e3c3625366591bc2ffc6e262976e" | 2419       | "2014-02-16 13:01:06 UTC" |
| 2       | "item name2" | "3e9dd9474dacb78afd607f9e0a3366" | 1298       | "2014-05-24 13:59:26 UTC" |
| 3       | "item name3" | "9b6c9e4a140284d3951681e9e047f6" | 9084       | "2014-06-21 00:18:21 UTC" |
| 4       | "item name4" | "a11faf5e63c1b02a3d4c2b5cbb7331" | 669        | "2014-05-02 03:44:08 UTC" |
| 6       | "item name6" | "6aa15471c373ddc8a6469e1c918f98" | 3556       | "2014-03-29 08:30:23 UTC" |

Execute Load Job

Finally, submit the load job. The job may take a couple of hours to run depending on the data size. Users need to specify the database and table where their data is stored.

It is recommended to specify --time-column option, since Treasure Data’s storage is partitioned by time (see also architecture) If the option is not given, the Data Connector will choose the first long or timestamp column as the partitioning time. The type of the column specified by --time-column must be either of long and timestamp type.

If your data doesn’t have a time column you may add it using add_time filter option. More details at add_time filter plugin.

$ td connector:issue load.yml --database td_sample_db --table td_sample_table

The above command assumes you have already created database(td_sample_db) and table(td_sample_table). If the database or the table do not exist in TD this command will not succeed, so create the database and table manually or use --auto-create-table option with td connector:issue command to auto create the database and table:

$ td connector:issue load.yml --database td_sample_db --table td_sample_table --time-column created_at --auto-create-table

You can assign Time Format column to the "Partitioning Key" by "--time-column" option.

You can load records incrementally by specifying columns in your table by utilizing the incremental_columns and last_record options.

  type: sqlserver
  host: sqlserver_host_name
  port: 1433
  user: test_user
  password: test_password
  database: test_database
  table: test_table
  incremental: true
  incremental_columns: [id, sub_id]
  last_record: [10000, 300]
  mode: append
  exec: {}

Then plugin will automatically recreate query and sort value at internal.

# when last_record wasn't given
    ...original query is here
ORDER BY id, sub_id

::: terminal
# when last_record was given
    ...original query is here
WHERE id > 10000 OR (id = 10000 AND sub_id > 300)
ORDER BY id, sub_id

If you’re using with scheduled execution, plugin will automatically generate last_record and hold it internally. Then you can use it at next scheduled execution.

  type: sqlserver

Config Diff
  - 20000
  - 400

`query` option can't available when you set `incremental: true`.

Only strings and integers are supported as incremental_columns.

Scheduled execution

You can schedule periodic Data Connector execution for periodic Microsoft SQL Server import. We carefully configure our scheduler to ensure high availability. By using this feature, you no longer need a cron daemon on your local data center.

Create the schedule

A new schedule can be created using the td connector:create command. The name of the schedule, cron-style schedule, the database and table where their data will be stored, and the Data Connector configuration file are required.

$ td connector:create \
    daily_sqlserver_import \
    "10 0 * * *" \
    td_sample_db \
    td_sample_table \

The `cron` parameter also accepts three options: `@hourly`, `@daily` and `@monthly`.

By default, schedule is setup in UTC timezone. You can set the schedule in a timezone using -t or --timezone option. The `--timezone` option only supports extended timezone formats like 'Asia/Tokyo', 'America/Los_Angeles' etc. Timezone abbreviations like PST, CST are *not* supported and may lead to unexpected schedules.

List the Schedules

You can see the list of scheduled entries by td connector:list.

$ td connector:list
| Name                    | Cron         | Timezone | Delay | Database     | Table           | Config                       |
| daily_sqlserver_import | 10 0 * * *   | UTC      | 0     | td_sample_db | td_sample_table | {"type"=>"sqlserver", ... } |

Show the Setting and History of Schedules

td connector:show shows the execution setting of a schedule entry.

% td connector:show daily_sqlserver_import
Name     : daily_sqlserver_import
Cron     : 10 0 * * *
Timezone : UTC
Delay    : 0
Database : td_sample_db
Table    : td_sample_table

td connector:history shows the execution history of a schedule entry. To investigate the results of each individual execution, use td job <jobid>.

% td connector:history daily_sqlserver_import
| JobID  | Status  | Records | Database     | Table           | Priority | Started                   | Duration |
| 578066 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-18 00:10:05 +0000 | 160      |
| 577968 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-17 00:10:07 +0000 | 161      |
| 577914 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-16 00:10:03 +0000 | 152      |
| 577872 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-15 00:10:04 +0000 | 163      |
| 577810 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-14 00:10:04 +0000 | 164      |
| 577766 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-13 00:10:04 +0000 | 155      |
| 577710 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-12 00:10:05 +0000 | 156      |
| 577610 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-11 00:10:04 +0000 | 157      |
8 rows in set

Delete the Schedule

td connector:delete will remove the schedule.

$ td connector:delete daily_sqlserver_import


Modes for out plugin

You can specify file import mode in out section of load.yml.

append (default)

This is the default mode and records are appended to the target table.

  mode: append

replace (In td 0.11.10 and later)

This mode replaces data in the target table. Any manual schema changes made to the target table will remain intact with this mode.

  mode: replace

Further Information

  • No labels