After a database upgrade, a report using datetime calculations does not complete due to an arithmetic overflow error. What is the best way to troubleshoot?

• A. Changing the report filter
• B. Reviewing error logs
• C. Verifying the columns' data types
• D. Checking that the data has refreshed

Answer: (C)

Datetime calculations depend on the exact data types and their valid ranges. After a database upgrade, the schema or how values are interpreted can change, so an arithmetic overflow often points to a mismatch or change in how the operands are stored. The best way to troubleshoot is to verify the data types of the columns involved in the calculation and how they’re used in the report’s query. Check that each operand is the expected type and that the calculation stays within the permissible range for that type. If you find a mismatch or a stricter/alternative type, apply a safe cast or conversion to a compatible type (for example, casting to datetime2 or date, or converting an integer representation to a date) so the arithmetic remains within bounds. After aligning the types, test with representative data to confirm the overflow is resolved.