Enable SQL Server Source Heartbeat
This document explains how to enable the heartbeat function during the incremental data synchronization phase when there is no write on the source, in order to display the correct latency in the console.
Overview
In scenarios where SQL Server serves as the source for data synchronization, extended periods without data changes can cause latency display issues in the console.
Enabling the heartbeat function addresses this by periodically generating new update events, ensuring that latency metrics are displayed accurately.
Two heartbeat modes are currently supported:
- CHECK_POS Mode: BladePipe periodically checks the source database and creates new heartbeat events without writing data.
- SEND_SQL Mode: BladePipe periodically executes SQL statements on a designated source-side heartbeat table to generate new update events.
Prerequisites
- BladePipe version ≥ 1.2.0.
- Required permissions vary by mode:
- CHECK_POS Mode
- SEND_SQL Mode
- The source database account must have SELECT permission.
- The source database account must have UPDATE permission.
- The source database account must have the db_owner role (if automatic CDC enablement is required).