Data Polling

This page outlines how to set up a Listener Config for data polling.

1. Overview

Version 5.4 of the Cinchy platform introduced data polling, which uses the Cinchy Event Listener to continuously monitor and sync data entries from your SQLServer or DB2 server into your Cinchy table. This capability makes data polling a much easier, effective, and streamlined process and avoids implementing the complex orchestration logic that was previous necessary.

This page outlines the necessary Listener Config values that need to be used prior to setting up your data sync.

2. Data Polling Listener Config

The following parameters should be included in your listener configuration entry when setting up a real time sync using data polling on your SQLServer or DB2 server.

2.1 Topic Column





Mandatory. The parameters here are used in a basic query which searches for all records in a particular table.

Note that in our example we need to use a sub-query to prevent an infinite loop if the "CursorColumn" parameter is not unique.

Example basic query:

FROM [SourceTable]
    FROM [SourceTable]
    ORDER BY Id)


Mandatory. This must contain at least the table name but can also contain Joined tables as written in SQL language.

Example: [Source Table]


Mandatory. Column name that is used in any 'WHERE' condition(s) and for ordering the result of a query

Example: [Id]


Mandatory. Minimum size of a batch of data per query. This can be larger to prevent infinite loops if the CursorColumn is not unique.

Example: 100


All filtering options used in any 'WHERE' condition(s) of the query

Example: "Name IS NOT NULL"


Mandatory. A list of columns that we want to show in a result.

Example:"Id", "Name"


The parameters here are used in more complex queries. In our example, we have 2 related tables, but want to show the contents of one of them based on the 'CursorColumn' from a second table. Since Timestamp values are not unique, we need to find all combinations of Id, Timestamp that match the filter condition in a subquery, and then join this result with the outer-query to get the final result. Note that in "ReturnDataConfiguration", our parameters area of concern is everything outside of first open parenthesis "(" and last closing parenthesis ")", i.e.:

) AS t INNER JOIN [Table1] ts ON ts.[Id] = t.[Id]
WHERE ts.[Id] > 0

Example complex query:

SELECT ts.[Id],ts.[Name] FROM
SELECT Id,Timestamp
FROM [Table2]
WHERE Timestamp IN (SELECT TOP (2)
FROM [Table2]
WHERE Timestamp > '2022-11-18 11:34:09 AM'
AND Timestamp <= '2022-
11-19 11:34:09 AM'
AND 1=1
ORDER BY Timestamp)
AND 1=1
) AS t
INNER JOIN [Table1] ts ON ts.[Id] = t.[Id]
WHERE ts.[Id] > 0


Mandatory. This is the alias for a subquery result table. It is used in 'JoinClause', and can be used in 'Columns' if we want to return values from a subquery table.

Example: "t"


Mandatory. Our result table to which we join the subquery result, plus the condition of the join.

Example: [Table1] ts ON ts.[Id] = t.[Id]


All filtering options used in any 'WHERE' conditions.

Example: "ts.[Id] > 0"


Mandatory. This is the column(s) that we want to order our final result by.

Example: "Id"


Mandatory. A list of columns that we want to show in the final result.

Example: "ts.[Id]" "ts.[name]"


Mandatory. This represents the delay, in second, between data sync cycles once it no longer finds any new data.

Example: 10


Optional, but recommended to mitigate data loss. See here for more information on this parameter.


Example Config

  "CursorConfiguration": {
    "FromClause": "[Source Table]",
    "CursorColumn": "Id > 0",
    "BatchSize": 100,
    "FilterCondition": "Name IS NOT NULL",
    "Columns": [
      "Id", "Name"
  "ReturnDataConfiguration": {
    "CursorAlias": "t",
    "JoinClause": "[Table1] ts ON ts.[id] = t.[id]",
    "FilterCondition": "ts.[id] > 0",
    "OrderByClause": "id",
    "Columns": [
  "Delay": 10
  "MessageKeyExpression": "id"

2.2 Connections Attributes Column




Mandatory. TSQL or DB2


Mandatory. This should be the connection string for your data source.

Example Config

  "databaseType": "TSQL",
  "connectionString": "Server=;Database=;User ID=cinchy;password=example;Trusted_Connection=False;Connection Timeout=30;Min Pool Size=10;",

3. messageKeyExpression

The messageKeyExpression parameter is an optional, but recommended, parameter that can be used to ensure that you aren't faced with a unique constraint violation during your data sync. This violation could occur if both an insert and an update statement happened at nearly the same time. If you choose not to use the messageKeyExpression parameter, you could face data loss in your sync.

This parameter was added to the Data Polling event stream in Cinchy v5.6.

Each of your Event Listener message keys a message key. By default, this key is unique for every message in the queue.

When the worker processes your Event Listener messages it does so in batches and, for efficiency and to guarantee order, messages that contain the same key will not be processed in the same batch.

The messageKeyExpression property allows you to change the default message key to something else.


  "MessageKeyExpression": "id"

Last updated

Was this helpful?