Data & Analytics
Airbyte SQL Server bulk loads can silently corrupt accented text
Compare INSERT and BULK paths before trusting non-ASCII text from Airbyte into SQL Server.
November 9, 2026
A load can finish successfully while customer names become unreadable. An Airbyte SQL Server destination report shows non-ASCII characters correct in INSERT mode and corrupted in BULK mode using Azure Blob staging. The reporter traced the difference to a format file declaring a legacy collation for character fields despite the bulk command specifying UTF-8. They tested a local collation patch; an upstream release containing it was not verified.
Isolate the load path
Capture the destination connector version, load_type, SQL Server collation, staging format file and a small multilingual fixture. Use strings with accented characters and punctuation, then compare source bytes, INSERT result and BULK result. Airbyte's destination guide documents both load types and the Azure Blob configuration required for BULK. A successful sync status cannot validate text fidelity.
Inspect the generated format file as well as BULK INSERT options. Microsoft documents format-file data formats; the bytes, field type and collation together determine how text is interpreted. Do not fix mojibake by transforming already corrupted report strings. Find the point where the bytes were decoded wrongly.
Contain the damage
For affected streams, compare a deterministic sample of primary keys and text fields to the source. If INSERT mode passes and BULK fails, switch the affected connection only after checking throughput and operational cost. Backfill the corrupted rows from the original source, and verify the corrected text before removing the alert.
Track the upstream issue and test a released connector build against the same fixture before returning to BULK. Keep the fixture in acceptance checks for future connector upgrades.
Adovo’s view
Encoding is a data contract, not a cosmetic display issue. If a pipeline changes a person's name while claiming success, it has broken trust at the boundary. Test the bytes that matter before optimizing the load path.
