One of my C# SQLCLR table valued function started to throw an exception with some recently added data to the database:
SQL Server Message 6260
system.overflowexception Arithmetic Overflow
How-i-fixed-it:
It turned out to be caused by a divison by 0 happening at runtime because of bad records in the data. I added some code to check for this which fixed the problem of the arithemtic overlow.
No comments:
Post a Comment