Two-way sync
Changes in InterSystems IRIS or Vertica instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS and Vertica in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want InterSystems IRIS's rows in Vertica, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in InterSystems IRIS where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in InterSystems IRIS sync into Vertica in real time, and result tables in Vertica sync back into InterSystems IRIS, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in Vertica sync into InterSystems IRIS, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Vertica and keep InterSystems IRIS focused on its operational workload.
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.
| InterSystems IRIS objects | Vertica objects | |
|---|---|---|
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Schemas Namespaces used to organize synced datasets by domain or source. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Tables Columnar tables; the primary read and write targets for syncs. | |
| Views SQL views expose curated slices of data for outbound replication. | Projections Sorted, encoded physical copies of table data that the optimizer selects at query time; they affect load and query behavior rather than being addressed directly. | |
| Schemas Schema organization scopes which tables a sync connection can see. | Views Logical views used to shape reads for downstream consumers. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Flex Tables Schema-flexible tables for semi-structured JSON data landed before modeling. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | External Tables Data queried in place on files or object storage without loading. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Vertica connection.
Changes in InterSystems IRIS or Vertica instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or Vertica data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single InterSystems IRIS or Vertica record.
Track your InterSystems IRIS ⇄ Vertica sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Vertica.
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 InterSystems IRIS and Vertica 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 InterSystems IRIS and Vertica 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 InterSystems IRIS and Vertica: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Stored Procedures and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Vertica: SQL over JDBC, ODBC, and ADO.NET drivers. Authentication: Database credentials, with LDAP, Kerberos, and OAuth options in enterprise deployments. Stacksync manages authentication, retries, and rate limits on both sides.
Vertica: Eon mode separates compute from communal object storage, letting subclusters scale independently of the data. InterSystems IRIS: InterSystems positions IRIS as the successor to Caché, and it is widely deployed under healthcare and financial applications. Stacksync's field mapping accounts for these differences between InterSystems IRIS and Vertica 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 InterSystems IRIS and Vertica records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed InterSystems IRIS and Vertica connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–Vertica integration in-house.
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and Vertica. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 386 integrations available for InterSystems IRIS and Vertica.