Installation Steps

GlueSync SQL to NoSQL for MS SQL Server

Prerequisites

In order to have GlueSync working on your MS SQL instance you will need to have:

  • valid user credentials with permissions of reading, writing to the target tables and respective database

Basic configuration example

This video tutorial will guide you through the basic configurations steps on setting up GlueSync for Microsoft SQL Server and Couchbase

The SQL to NoSQL module can be customized by using a configuration file, in JSON format. The file name to use must be specified as parameter when launching the app, with the -f or --file tokens. The file should be composed by union of common configuration file (see here Installation Steps) and source/destination specific configuration:

{
  ...
  "mssql": {
    "temporaryTableNamePrefix": "table_prefix",
    "statePreservationTableNamePrefix": "state_prefix"
  },

  "sourceChangeRetention": 5
}

Microsoft SQL Server specific configurations are listed under the mssql property:

  • temporaryTableNamePrefix (optional): allow to specify a custom prefix for temporary table created by GlueSync to improve performance. Typical use case is to allow multiple instances of GlueSync to run from the same source, thus avoiding conflicts at runtime;

  • statePreservationTableNamePrefix (optional): allow to specify a custom prefix for state presevation table created by GlueSync to keep a checkpoint of processed changes. Typical use case is to allow multiple instances of GlueSync to run from the same source, thus avoiding conflicts at runtime;

  • sourceChangeRetention (optional): defaults to 5. Number of retention days preserved into the MS SQL Server change tracking system;

Looking for data modelling features or other options?

For more detailed configurations options, including the ability to perform data modelling, please have a look at the dedicated Data modelling section when sourcing from a RDBMS.