mar.ko (9/3/2015)
Luis Cazares (9/3/2015)
Not really strange as it converts to an int within the IIF before being converted to a bigint.the problems caused by ISNUMERIC
No excuse on Microsoft's part....should have been fixed long ago.
I saw a post on this site where someone created their own "IsBigInt" function.....
but there was way too much code and therefore overhead for me to want to use it.
Native functions are likely 10x faster than functions written in T-SQL.
Why should they fix it if it's not broken? It's not an ISINTEGER function, it just tells you if a value is a valid numeric for any of the datatypes available. The article that I linked on my previous post shows a simple validation to check if it's an all-digits string which most of the time would be able to fit a bigint.