Installation steps

Gluesync SQL to NoSQL for Sybase

Prerequisites

To have Gluesync working on your Sybase instance you will need to have:

valid user credentials with permission to read, and write to the target tables and respective database

Basic configuration example

This video tutorial will guide you through the basic configuration steps on setting up Gluesync for Microsoft SQL Server and Couchbase (Sybase setup is literally similar)

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 a parameter when launching the app, with the -f or --file tokens. The file should be composed of the union of the common configuration files (see here Installation steps) and source/destination specific configuration:

{
  ...
  "sourcePort": "5000",
  ...
  "sourceChangeRetention": 5
  ...

  "sybase": {
    "tableKeys": {
      "articles": ["id1", "id2"],
      "drivers": ["driver_unique_id"],
      "customers": [
          "customer_name",
          "customer_surname",
          "customer_age",
          "customer_id"
        ]
    }
  }
}

You can also specify a few other options that apply to this configuration, like:

sourceChangeRetention (optional): defaults to 5. Number of retention days preserved in the Gluesync GDC action_logs table inside your Sybase database;

Sybase-specific configurations are listed under the sybase property.

tableKeys: is the object that represents the key-value pair list of tables and its columns that compose the clustered (compound) index or the column Gluesync will use as a primary key. To read more about this feature we suggest you have a look at the following link.

Looking for data modeling features or other options?

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