A SUM() or multiplication on an INT column produces a result exceeding 2,147,483,647. DECIMAL precision and scale settings are too small for the computed value. A date calculation results in a date outside SQL Server's supported range

Step 1: Cast the column to a larger type before aggregation: SELECT SUM(CAST(col AS BIGINT)) FROM table;. Step 2: Increase DECIMAL precision: change DECIMAL(10,2) to DECIMAL(18,2) in the column definition or calculation.. Step 3: For date overflows, validate dates before calculation: SELECT * FROM table WHERE date_col > '1753-01-01' AND date_col < '9999-12-31';

Medium severitydata integrity

Power BI Refresh Error:
8115

Q: How do I find the INT column causing overflow?

Run the query in SSMS with CAST to BIGINT on each summed column one at a time, or check execution plan for the operator where overflow occurs.

Q: Can Power BI DAX cause error 8115?

In DirectQuery mode, DAX measures that generate SQL aggregations can trigger 8115 if the underlying SQL Server column type is too small. In Import mode, Power BI uses its own engine and handles larger numbers.

Q: Is BIGINT always the right fix?

For monetary calculations, use DECIMAL or NUMERIC to avoid precision loss. BIGINT handles integer values up to 9.2 quintillion, which is sufficient for most row counts and counters.

What does this error mean?

A calculation produced a value outside the range of the target data type — the result is too large or too small to store.

Common causes

1A SUM() or multiplication on an INT column produces a result exceeding 2,147,483,647
2DECIMAL precision and scale settings are too small for the computed value
3A date calculation results in a date outside SQL Server's supported range

How to fix it

1Step 1: Cast the column to a larger type before aggregation: SELECT SUM(CAST(col AS BIGINT)) FROM table;
2Step 2: Increase DECIMAL precision: change DECIMAL(10,2) to DECIMAL(18,2) in the column definition or calculation.
3Step 3: For date overflows, validate dates before calculation: SELECT * FROM table WHERE date_col > '1753-01-01' AND date_col < '9999-12-31';

Frequently asked questions

How do I find the INT column causing overflow?

Run the query in SSMS with CAST to BIGINT on each summed column one at a time, or check execution plan for the operator where overflow occurs.

Can Power BI DAX cause error 8115?

In DirectQuery mode, DAX measures that generate SQL aggregations can trigger 8115 if the underlying SQL Server column type is too small. In Import mode, Power BI uses its own engine and handles larger numbers.

Is BIGINT always the right fix?