Source Metadata Columns

When you're consolidating data from multiple sources, it's not always enough to just move the rows - you also need to know where they came from. Without that context, compliance checks get harder, debugging slows down, and downstream apps lose critical signals. Artie makes it simple to retain that lineage.

You can now enable source metadata columns in Advanced Settings. When turned on, Artie appends an extra column to replicated tables containing details like transaction ID, log sequence number, schema, table, and database name.

For example:

• A fintech consolidating dozens of sharded MySQL databases into one Snowflake table can track exactly which shard each row came from.
• A healthcare company can capture source database and table information for HIPAA audit logs.
• A payments team can tie replicated rows back to original transaction IDs for fraud analysis.

Why this matters:

• Traceability: See exactly where each row originated, even across shards.
• Auditability: Support compliance and security workflows with source-side context.
• Debugging: Isolate discrepancies quickly by filtering on schema/table metadata.
• Flexibility: Build custom fraud detection, routing, or monitoring logic using metadata.