Changelog

To further enhance the data integrity built into our pipeline, we've added another guardrail: verifying the number of rows affected during each database operation.

For example, during merge steps (such as in Snowflake), we confirm ROWS_LOADED from copy commands and validate the totals for inserted, updated, or deleted rows. This approach reinforces the robustness of our data replication process and it's another way we catch issues early and ensure replication integrity.

You can now control how many rows Artie processes at a time during backfills. The default is now 25,000 rows per chunk (up from 5,000), but you can tune this based on performance vs. load tradeoffs.

Why backfill batch size matters:

Backfills aren’t one-size-fits-all. Some teams want speed. Others are sensitive to database load and tiptoeing around a production DB at 2am. Until now, everyone got the same batch size of 5,000 rows per chunk. Now you can tune backfills to match your style:

• The default is 25,000 rows - we benchmarked a bunch of sizes. 25,000 rows won out. So that’s our new default
• You have control - adjust the batch size to fit your environment

How to tune batch size based on your workload:

• Speed up backfills: Larger chunks = fewer queries, can improve throughput, but overly large chunks can backfire. It’s about finding balance.
• Reduce DB load: Smaller chunks = faster queries, lower impact on source

Need help tuning batch size?

If you're unsure what batch size is right for your workload, reach out - we'll help you tune it.

Some tables are weird. No primary key (PK), maybe just a unique index or some composite hack someone added in 2017. Until now, those were off-limits for replication.

You can now override PK requirements by specifying a unique index - including composite indexes. Artie will respect the exact column order to ensure optimal performance.

Why index-based PK overrides matter:

Not every table has a clean PK. Some use unique indexes or composite keys that aren’t formally declared as PKs. Until now, these tables were difficult (or impossible) to replicate. This change addresses one of the most common blockers for CDC at scale.

What’s changed:

• PK override: Define row identity with a unique index
• Use composite keys - even if unofficial or unenforced
• Preserve the exact index column order, which affects how changes are captured and impacts query performance during replication (e.g., email, account_id, created_at)

This unlocks flexible replication for legacy systems, denormalized tables, and high-volume sources - without compromising performance.

When to use index-based keys:

• Your table lacks a formal PK, but has a unique constraint or index
• You rely on composite keys to identify rows
• You’re dealing with legacy systems or data models that weren’t built with CDC in mind

How to enable key overrides:

Reach out to enable key overrides - we'll help define your index logic and validate it during setup.

With our Oracle Fan-in feature, you can now easily replicate data from thousands of Oracle sources - without painful manual setups or infrastructure overload. Fan-in reduces your Kafka topic sprawl, lowers infrastructure costs, and simplifies real-world, complex data replication.