When AdaptDDL creates a new table on a Microsoft SQL Server & Snowflake target from a Sybase source, HVR automatically adds DEFAULT constraints to NOT NULL columns when no explicit default exists on the source table alongside this when a default is specified it's not accurately added to the target.

Current behaviour:

• Source table contains NOT NULL columns without user-defined defaults.
• AdaptDDL creates the table on SQL Server.
• HVR automatically adds defaults based on datatype:
  • Character columns → default ' '
  • Numeric columns → default 0
• Target schema therefore differs from the source schema.

Issue:

• The generated target DDL is not an accurate representation of the source DDL.
• Additional default constraints can affect application behaviour, data quality controls, and downstream schema comparisons.
• Customers may require schema parity between source and target environments.

Requested enhancement:

• Provide an AdaptDDL option to preserve source column definitions exactly.
• Allow disabling automatic creation of datatype-based defaults on NOT NULL columns.
• Alternatively, only create DEFAULT constraints when an explicit default exists on the source table.

Expected behaviour: If a source column is defined as:

Business impact:

• Prevents schema drift between source and target.
• Simplifies DDL comparisons and governance.
• Avoids unintended data population through system-generated defaults.
• Better supports migrations where source DDL fidelity is required.