Error map
8114 SQL Server Msg 8114: Error converting data type varchar to numeric
SQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
SQL Server: Conversion failed when converting the varchar value 'x' to data type int. (Msg 245)
SQL Server tried to convert text to a number (often implicitly) and hit a non-numeric value.
SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115)
A value or calculation exceeds the target data type’s range.
Snowflake: Numeric value 'X' is not recognized
A text value couldn't be converted to a number while loading or casting.
Numbers sort wrongly (1, 10, 2): VARCHAR column sorted as text
A numeric-looking column stored as text sorts alphabetically, so "10" comes before "2".
SQL Server Msg 209: Ambiguous column name
A column exists in more than one table of the query and isn't qualified.
CASE expression returns mixed types: conversion failed / types cannot be matched
The branches of a CASE expression produce incompatible data types (text and number, date and string).
SQL Server Msg 242: The conversion of a varchar data type to a datetime data type resulted in an out-of-range value
A date string couldn't be converted because it's invalid or in the wrong format for the session language.
GROUP_CONCAT / STRING_AGG result truncated or fails (group_concat_max_len, string length limit)
An aggregated string is cut off at 1024 characters (MySQL) or fails with a size error (SQL Server STRING_AGG, 8000 bytes).
Two steps away (22)
ERROR: invalid input syntax for type integer: "abc"
A string couldn’t be converted to the column’s type (integer, numeric, boolean, date…).
SQL Server: Login failed for user 'x'. (Error 18456)
SQL Server rejected the login — wrong password, wrong authentication mode, or a disabled/missing login.
SQL Server: Invalid object name 'x'. (Msg 208)
The table/view doesn’t exist in the current database or schema.
ERROR: numeric field overflow — A field with precision 5, scale 2 must round to an absolute value less than 10^3
A number doesn’t fit the column’s numeric(precision, scale) or integer range.
SQL Server: Invalid column name 'x'. (Msg 207)
SQL Server can’t find the column — typo, missing migration, or a string in double quotes with QUOTED_IDENTIFIER ON.
SQL Server: Violation of PRIMARY KEY constraint 'x'. Cannot insert duplicate key in object 'y'. (Msg 2627)
An insert duplicated a primary key or unique constraint value.
Snowflake SQL compilation error: Object 'X' does not exist or not authorized
The table/view/schema name can't be resolved in the current role, database and schema context, or the role lacks privileges.
Snowflake: No active warehouse selected in the current session
The query needs compute, but the session has no warehouse set or usable.
BigQuery load job failed: schema mismatch / Provided Schema does not match table
A load job's file schema or column types don't match the destination table.
Query returns far too many rows: accidental Cartesian product (missing JOIN condition)
Two tables were joined without a condition, so every row of one pairs with every row of the other.
5 / 2 = 2: integer division silently truncates the result
Dividing two integers returns an integer in most databases, so decimals are dropped.
COUNT(column) ignores NULLs: counts differ from COUNT(*)
`COUNT(col)` counts only non-NULL values, while `COUNT(*)` counts rows, so totals don't match.
Column reference is ambiguous / Column 'id' in field list is ambiguous (MySQL 1052)
A column name exists in more than one joined table, so the database doesn’t know which one you mean.
MySQL ERROR 1066 (42000): Not unique table/alias: 'x'
The same table or alias appears twice in a FROM/JOIN without distinct aliases.
LEFT JOIN returns fewer rows: a WHERE filter on the right table turns it into an INNER JOIN
A condition on the right-hand table in WHERE removes the NULL-extended rows that a LEFT JOIN was supposed to keep.
AttributeError: 'X' object has no attribute 'y'
You accessed an attribute or method that doesn’t exist on that object type.
java.lang.ClassCastException: class A cannot be cast to class B
An object was cast to a type it isn’t.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
A Node API got an argument of the wrong type — usually undefined because an env var or config value is missing.
Dates mixed up: dd/mm/yyyy vs mm/dd/yyyy, ISO 8601 recommended
A date string like 03/04/2026 is read as March 4th or April 3rd depending on locale, so rows get wrong dates or conversion errors.
SQL Server Msg 515: Cannot insert the value NULL into column 'X', table 'Y'; column does not allow nulls
An INSERT or UPDATE tried to put NULL into a NOT NULL column that has no default.
SQL Server Msg 5123: CREATE FILE encountered operating system error 5 (Access is denied) while attempting to open the physical file
SQL Server's service account can't read or write the .mdf/.ldf file when attaching or restoring.
MySQL ERROR 1406: Data too long for column
The value is longer than the column allows (e.g. 300 characters into VARCHAR(255)), and strict mode rejects it instead of truncat…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError