SQL Server to Hive
real-time replication
TwinCommit replicates Microsoft SQL Server to Apache Hive in real time by reading the SQL Server transaction log and applying every committed change exactly once and in commit order. Use it to feed Hive with live SQL Server data for analytics, AI and reporting, with no triggers or capture tables on the source.
SQL Server
log reader
commit-ordered · exactly-once
Hive
native writer
How capture works on SQL Server
TwinCommit reads the active and backed-up transaction log directly, so you do not need SQL Server Agent CDC jobs or change tables.
Prerequisites
- ✓FULL recovery model
- ✓Primary key on each replicated table
- ✓VIEW SERVER STATE and db_owner on the source database
How apply works on Hive
Changes are written as ORC delta files and committed with Hive ACID MERGE, or as Iceberg snapshots through the Hive Metastore, depending on table format.
Requirements
- ✓Transactional (ACID) tables or Iceberg tables
- ✓HiveServer2 JDBC endpoint
- ✓Write access to the warehouse location
Setup
Set up SQL Server → Hive in four steps
- 1
Prepare SQL Server
Run twincommit check. It verifies full recovery model and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Hive
Add a target block for Hive. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: sqlserver
dsn: ${SOURCE_DSN}
target:
type: hive
jdbc_url: jdbc:hive2://hs2.internal:10000/default
table_format: iceberg
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SQL Server to Hive replication FAQ
How does TwinCommit replicate SQL Server to Hive?
+
TwinCommit reads changes from the SQL Server transaction log, buffers them per transaction, and applies each committed transaction to Hive in commit order. Changes are written as ORC delta files and committed with Hive ACID MERGE, or as Iceberg snapshots through the Hive Metastore, depending on table format.
Does SQL Server to Hive replication need triggers or capture tables?
+
No. TwinCommit reads the SQL Server log directly and creates no objects in the source database.
Is SQL Server to Hive replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Hive transaction as the data, so a crash or restart never loses or duplicates a transaction.
What SQL Server versions are supported?
+
SQL Server 2016–2025 · Azure SQL Managed Instance · Azure SQL Database (target).
Stream SQL Server to Hive today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.