Ssis-661 |link| Page

EXEC catalog.start_execution @execution_id;

Keep a test Windows account that mirrors the production service account. Use it to validate permissions before rolling out changes to production. SSIS-661

:

After applying the patch, run the “Integration Services Catalog – Validate” command ( catalog.validate_package ) on the affected packages. The validation will now surface any remaining conversion warnings. EXEC catalog

| Layer | What’s Going Wrong | |-------|-------------------| | | Returns a Unicode ( DT_WSTR ) buffer regardless of the column definition because the OLE DB driver for Oracle/MySQL always uses SQL_WVARCHAR . | | Metadata Propagation | SSIS metadata engine infers the target data type from the destination schema ( VARCHAR → DT_STR ). | | Runtime Conversion | The engine performs an in‑memory conversion using WideCharToMultiByte . When the source string contains a character that cannot be represented in the target code page, SSIS‑661 fails to raise a proper exception and either truncates incorrectly or corrupts the internal row buffer. | | Buffer Management | The conversion routine miscalculates the required buffer length for multi‑byte characters, causing buffer overruns that manifest as the “loss of data” error or, on some builds, a hard crash ( 0xC0047086 ). | The validation will now surface any remaining conversion

is a classic example of how subtle Unicode handling bugs can ripple through large data‑integration pipelines, causing silent data corruption. By: