Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Any idea why ISNUMERIC('0D0') = 1 is TRUE in SQL Server 2008?
I’m validating ID numbers from another system, which sometimes contain letters that we don’t want to bring over, but this combination is tripping up the code (the specific ID that it thinks is numeric is “005406257D6”). Downstream we’re doing CONVERT(BIGINT, @val), which is obviously choking when it finds these “D” values.
What special case am I hitting, and how do I account for it?
Basically, IsNumeric is useless – all it verifies is that the string can be converted to any of the numeric types. In this case, “0D0” can be converted to a float. (I can’t remember the reason, but effectively “D” is a synonym for “E”, and means it’s scientific notation):
If you want to verify that it’s just digits, then
not @val like '%[^0-9]%'would be a better test. You can improve this further by adding a length check also.