Two-way sync
Changes in Exasol or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol and Sysaid in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Whatever Sysaid is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.
Stacksync syncs Service Requests, Problems, Changes, Users from Sysaid into tables in Exasol continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Exasol can also be written back into fields in Sysaid where the tool can use them.
Segments, scores, or reference values computed in Exasol sync back onto records in Sysaid, putting analysis where the work happens.
A continuously synced copy in Exasol preserves a queryable record even as data ages out of Sysaid or gets changed inside it.
Records and events from Sysaid land in Exasol as queryable tables, current within seconds and ready to join with the rest of the warehouse.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Exasol objects | Sysaid objects | How this pairing syncs | |
|---|---|---|---|
| Tables Primary sync target; columnar relational tables written with standard SQL. | Changes Change records (type=change) with approval and scheduling fields; synced two-way to drive CAB review and deployment workflows. | Tables is specific to Exasol and Changes to Sysaid — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. | Views is specific to Exasol and Users to Sysaid — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. | Virtual schemas is specific to Exasol and Assets to Sysaid — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Configuration Items (CIs) CMDB entries and their relationships; synced with an external CMDB or asset database for one inventory view. | UDF scripts is specific to Exasol and Configuration Items (CIs) to Sysaid — each maps to any object or custom field on the other side. | |
| Users and roles Grant read/write access for the dedicated integration account. | Companies Customer and department organizations that scope tickets and users; mapped to Accounts in a CRM or org tables in a database. | Users and roles is specific to Exasol and Companies to Sysaid — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Custom Fields Org-specific fields on service records, discoverable through the API so mappings can be generated without hardcoding names. | Schemas is specific to Exasol and Custom Fields to Sysaid — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is written to Sysaid through its API, with automatic retries and rate-limit backoff.
DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.
DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Sysaid connection.
Changes in Exasol or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol or Sysaid data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Exasol or Sysaid record.
Track your Exasol ⇄ Sysaid sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol and Sysaid.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Exasol and Sysaid with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Exasol and Sysaid objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and Sysaid: authenticate both systems, choose the objects to sync (such as Exasol's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Sysaid: List endpoints are paginated with a limit parameter, so full syncs must page through large result sets rather than pulling everything in one call. Exasol: Bulk loading uses the IMPORT statement, which is more efficient than row-by-row inserts for sync workloads. Stacksync's field mapping accounts for these differences between Exasol and Sysaid without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Exasol and Sysaid records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Exasol and Sysaid connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Exasol–Sysaid integration in-house.
Yes — Stacksync ships production-grade connectors for both Exasol and Sysaid. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. On Sysaid: Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature; otherwise poll the /sr endpoint filtering on update_time.gte. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 437 integrations available for Exasol and Sysaid.