8114 SQL Origin: Data OSI layer 7 · Application Last updated 18 Nov 2026

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.

Exact message you may see Error converting data type varchar to numericError converting data type nvarchar to numericError converting data type varchar to floatMsg 8114, Level 16
Seen on: SQL Server SQL

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

  1. Locate rows: WHERE TRY_CONVERT(decimal(18,2), col) IS NULL AND col IS NOT NULL
  2. Clean the data before converting
  3. Use TRY_CAST for tolerant conversions

Detailed fix by platform

SQL

  1. SELECT col FROM t WHERE TRY_CONVERT(decimal(18,2), col) IS NULL AND col IS NOT NULL;

How to diagnose

  1. Bad rows — Found?
  2. Separators — Present?
  3. 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:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

100038 — Snowflake: Numeric value 'X' is not recognized (SQL)100038209 — SQL Server Msg 209: Ambiguous column name (SQL)209242 — SQL Server Msg 242: The conversion of a varchar data type to a datetime data type resulted in an out-of-range value (SQL)242245 — SQL Server: Conversion failed when converting the varchar value 'x' to data type int. (Msg 245) (SQL)2458115 — SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115) (SQL)8115CASE — CASE expression returns mixed types: conversion failed / types cannot be matched (SQL)CASEGROUP_CONCAT — GROUP_CONCAT / STRING_AGG result truncated or fails (group_concat_max_len, string length limit) (SQL)GROUP_CONCATsorting — Numbers sort wrongly (1, 10, 2): VARCHAR column sorted as text (SQL)sorting8114

Explore the map of this error Full error map →

🧠 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.