An Azure managed PostgreSQL database service for app development and deployment.
Decimal or numeric issues in Azure Data Factory pipelines are commonly caused by mismatches between source/target data types or how null/empty values and precision/scale are handled during copy.
For numeric/decimal columns being multiplied or otherwise changed when moving data via Integration Runtime:
- Verify precision/scale definitions
- Check the PostgreSQL column definitions (NUMERIC/DECIMAL precision and scale).
- Check the corresponding sink column definitions (for example, in Azure SQL, Synapse, or SQL Server) and ensure they match the same precision and scale.
- Mismatched precision/scale can cause rounding or unexpected numeric transformations.
- Check for empty-string or null handling in numeric columns
- When using staged copy/PolyBase into Synapse or SQL-based sinks, empty strings in numeric columns can cause errors or unexpected behavior.
- If using PolyBase in the sink, set use type default to
falsein the copy activity’s PolyBase settings so that empty strings are not forced into numeric defaults that could distort values.
- Review transformations in the pipeline
- Inspect Mapping Data Flows, Derived Columns, or any expressions that might be multiplying or scaling numeric values (for example, implicit casts, arithmetic operations, or default values).
- Remove or correct any transformation that changes the numeric scale unintentionally.
- Validate with a minimal test
- Create a small test table in PostgreSQL with known numeric values.
- Run a simple copy activity with no transformations and compare source vs. sink values to identify where the multiplication occurs (source, IR, or sink).
If the issue persists only with a specific Integration Runtime version, capture a minimal reproducible pipeline and open a support case so that the behavior can be compared against expected numeric handling.
References:
- Troubleshoot the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors in Azure Data Factory and Azure Synapse
- Troubleshoot self-hosted integration runtime
- KB2929832 - FIX: Decimal precision is incorrect when you calculate based on size of scale in SQL Server 2012 or SQL Server 2014 MDS
- KB3097970 - FIX: Sp_describe_undeclared_parameters returns incorrect result when the undeclared parameter targets a decimal column
- how to fix decimal code in sql - Microsoft Q&A
- Column Data size issue - Microsoft Q&A
- Not able to find the proper issue field - Microsoft Q&A
- How do I fix an SQL Server issue - Microsoft Q&A
- I just cant find a fix to this error. - Microsoft Q&A