ISNUMERIC()

External Article

Is It Time To Stop Using IsNumeric()?

  • Article

The old system function IsNumeric() often causes exasperation to a developer who is unfamiliar with the quirks of Transact SQL. It seems to think a comma or a number with a 'D' in the midde of it is a number. Phil Factor explains that though IsNumeric has its bugs, it real vice is that it doesn't tell you which of the numeric datatypes the string parameter can be coerced into, and because it doesn't check for overflow. Phil comes to the rescue with a couple of useful alternatives, one of which works whatever version of SQL Server you have, and which tell you what datatype the string can be converted to.

2017-08-21

4,500 reads

Blogs

The Book of Redgate: Spread across the world

By

This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...

Merry Christmas

By

Today is Christmas and while I do not expect anybody to actual be reading...

Self-Hosting a Photo Server the Whole Family Can Use

By

Until recently, my family's 90,000+ photos have been hidden away in the depths of...

Read the latest Blogs

Forums

SQL Server 2025 Backup Compression Algorithm

By Johan Bijnens

Comments posted to this topic are about the item SQL Server 2025 Backup Compression...

The Large Encoded Value

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Large Encoded Value

The Side Job

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Side Job

Visit the forum

Question of the Day

The Large Encoded Value

I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?

See possible answers