ClickHouse to Sharepoint integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between ClickHouse and Sharepoint: authenticate both systems, choose the objects to sync (such as ClickHouse's Tables (MergeTree family) and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on ClickHouse: No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source. On Sharepoint: Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last deltaLink; change-notification subscriptions (push webhooks) POST near-real-time notifications for list and drive/root changes to a notification URL and must be renewed before they expire. Classic SharePoint list webhooks are also available. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the ClickHouse side: Databases, Views, Materialized views, Distributed tables, plus custom fields where ClickHouse exposes them. On the Sharepoint side: List items, Drive items (document libraries), Columns and content types, Permissions and sharing. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for ClickHouse and Sharepoint: One dataset, kept consistent both ways; Where Sharepoint holds the file inventory: make it queryable; Where ClickHouse computes the labels: push them onto the files. Where the same dataset lives as a file in Sharepoint and a table in ClickHouse, a change on either side propagates to the other, ending the drift between the file people read and the table people query.

ClickHouse: Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available. Authentication: Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS. Sharepoint: Microsoft Graph REST API (graph.microsoft.com/v1.0 and beta) covering SharePoint sites, lists, list items, columns, content types, and document-library drives and drive items; plus the classic SharePoint REST API (_api/web) and CSOM. Supports Graph JSON $batch (up to 20 requests per call). Authentication: OAuth 2.0 via the Microsoft identity platform (Microsoft Entra ID). An app registration holds delegated or application (app-only) scopes such as Sites.Read.All, Sites.ReadWrite.All, Sites.Selected, Sites.Manage.All, or Sites.FullControl.All, plus Files.ReadWrite.All for drive content; application permissions require tenant admin consent. Stacksync manages authentication, retries, and rate limits on both sides.