Skip to main content
Database Administrators

Return to Question

added 26 characters in body
Source Link
lifeisajourney
lifeisajourney
  • 601
  • 6
  • 19

We have a stored procedure that uses SUM on an Int column in the SELECT statement. We have a few cases where for one of the parameter values, the SUM(integer column) exceeds the Int range and therefore throws an error

Arithmetic overflow error converting expression to data type int

The solution to this would be to convert the column to bigint in the sum function i.e. Sum(Convert(BigInt, column)). But since this is happening for a few specific cases at this point and not for all the cases, i'm concerned that I'll end up penalizing the other cases where this conversion is not needed. How much performance difference does conversion usually make? Is there any other way to handle this issue? Thanks!

We have a stored procedure that uses SUM on an Int column. We have a few cases where for one of the parameter values, the SUM(integer column) exceeds the Int range and therefore throws an error

Arithmetic overflow error converting expression to data type int

The solution to this would be to convert the column to bigint in the sum function i.e. Sum(Convert(BigInt, column)). But since this is happening for a few specific cases at this point and not for all the cases, i'm concerned that I'll end up penalizing the other cases where this conversion is not needed. How much performance difference does conversion usually make? Is there any other way to handle this issue? Thanks!

We have a stored procedure that uses SUM on an Int column in the SELECT statement. We have a few cases where for one of the parameter values, the SUM(integer column) exceeds the Int range and therefore throws an error

Arithmetic overflow error converting expression to data type int

The solution to this would be to convert the column to bigint in the sum function i.e. Sum(Convert(BigInt, column)). But since this is happening for a few specific cases at this point and not for all the cases, i'm concerned that I'll end up penalizing the other cases where this conversion is not needed. How much performance difference does conversion usually make? Is there any other way to handle this issue? Thanks!

Source Link
lifeisajourney
lifeisajourney
  • 601
  • 6
  • 19

Convert an Int column to BigInt in a stored procedure in SQL Server 2012

We have a stored procedure that uses SUM on an Int column. We have a few cases where for one of the parameter values, the SUM(integer column) exceeds the Int range and therefore throws an error

Arithmetic overflow error converting expression to data type int

The solution to this would be to convert the column to bigint in the sum function i.e. Sum(Convert(BigInt, column)). But since this is happening for a few specific cases at this point and not for all the cases, i'm concerned that I'll end up penalizing the other cases where this conversion is not needed. How much performance difference does conversion usually make? Is there any other way to handle this issue? Thanks!