SQL Server Msg 8114: Error converting data type varchar to numeric
A text value that isn't a valid number was converted to DECIMAL/NUMERIC.
Error converting data type varchar to numericError converting data type nvarchar to numericError converting data type varchar to floatMsg 8114, Level 16 Meaning
Find bad rows with TRY_CONVERT / ISNUMERIC (careful: ISNUMERIC accepts '$' and ','), strip formatting, and fix the data load. Culture-specific decimals (1,5) are a common cause.
Common causes
- Non-numeric text (empty string, 'N/A')
- Thousands separator or currency symbol
- Decimal comma
- Precision/scale too small for the value
- Implicit conversion in a join
⚡ Quick fix
- Locate rows:
WHERE TRY_CONVERT(decimal(18,2), col) IS NULL AND col IS NOT NULL - Clean the data before converting
- Use
TRY_CASTfor tolerant conversions
Detailed fix by platform
SQL
SELECT col FROM t WHERE TRY_CONVERT(decimal(18,2), col) IS NULL AND col IS NOT NULL;
How to diagnose
- Bad rows — Found?
- Separators — Present?
- Precision — Enough?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026