SQL Server "String or Binary Data Would Be Truncated": Fix Msg 8152 & 2628

By Sharon Ben-Moshe · September 20, 2026 · 1 min read

Sharon Ben-Moshe is the founder of sqlfmt, a browser-based SQL formatter and validator with misspelled-keyword suggestions across PostgreSQL, MySQL, SQLite, SQL Server, and BigQuery.

Fix SQL Server Error 8152 and 2628: String or binary data would be truncated. Discover how to identify the offending column and increase column size.

Quick answer

This error occurs when attempting to insert or update a string or byte array longer than the target column's defined length (e.g. inserting 60 characters into VARCHAR(50)). On SQL Server 2019+, error Msg 2628 explicitly lists the table, column, and truncated value. On older versions, enable trace flag 460 or query column LEN() to identify the offending payload.

FAQs

What is the difference between SQL Server Msg 8152 and Msg 2628?

Msg 8152 was the legacy, notorious message that gave no column name. Starting in SQL Server 2019 (and 2016 SP2 CU6 / 2017 CU12), Microsoft introduced Msg 2628, which states: 'String or binary data would be truncated in table X, column Y. Truncated value: Z'.

How do I enable verbose truncation messages on SQL Server 2017?

Run `DBCC TRACEON (460, -1);` or enable the database-scoped configuration: `ALTER DATABASE SCOPED CONFIGURATION SET VERBOSE_TRUNCATION_WARNINGS = ON;`.

Can I silently truncate text instead of throwing an error?

Yes, by wrapping the input with `LEFT(input_column, 50)`. However, silently truncating data often corrupts email addresses, hash tokens, or JSON payloads and is discouraged.

Does VARCHAR(MAX) prevent truncation errors?

Yes, VARCHAR(MAX) can store up to 2GB of data. However, using MAX indiscriminately prevents index key creation and degrades memory grant estimates.

SQL Errors

Fix BigQuery "Unrecognized Name" Error: Scoping and Syntax Rules

By Sharon Ben-Moshe · Sep 29, 2026

Fix Google BigQuery's "Unrecognized name: column" error. Learn alias visibility rules across WHERE and QUALIFY, case sensitivity, and struct unnesting.

Read post

SQL Errors

SQLite "Datatype Mismatch" (Error 20): Type Affinity and Strict Tables

By Sharon Ben-Moshe · Sep 26, 2026

Understand SQLite Error 20 (datatype mismatch). Learn how SQLite type affinity, CHECK constraints, and STRICT tables enforce data integrity.

Read post

SQL Errors

Try it now

Paste your SQL into sqlfmt — format, validate, and catch typos free in your browser.

Open SQL Formatter →

Key takeaways

Upgrade or configure VERBOSE_TRUNCATION_WARNINGS = ON to receive modern Error 2628 with exact column names.

Find violating source rows using LEN(column_name) > max_length in a diagnostic query.

Expand column definitions with ALTER TABLE ... ALTER COLUMN when inputs legitimately require more space.

Remember that NVARCHAR uses 2 bytes per character; check whether third-party APIs send multi-byte emojis or accents.

Enabling verbose truncation diagnostics

If running SQL Server 2019 or later, verbose messages are enabled by default under database compatibility level 150. For older instances supporting trace flag 460:

Enabling verbose truncation errors in SQL Server

-- Enable at the database level (SQL Server 2017 CU12+ / 2019)
ALTER DATABASE SCOPED CONFIGURATION
SET VERBOSE_TRUNCATION_WARNINGS = ON;

-- Output now changes from vague Msg 8152 to informative Msg 2628:
-- "String or binary data would be truncated in table 'SalesDB.dbo.Customers',
--  column 'PostalCode'. Truncated value: '98101-445892'."

Pinpointing the offending row in batch staging tables

When loading bulk CSV or API data into staging tables with unrestricted columns before inserting into destination tables, use LEN() to locate the violators:

Finding violating strings before insert

-- Inspect staging data against production column limits
SELECT
  staging_id,
  customer_code,
  LEN(customer_code) AS actual_length,
  postal_code,
  LEN(postal_code) AS postal_length
FROM staging_customers
WHERE LEN(customer_code) > 20   -- Target column is VARCHAR(20)
   OR LEN(postal_code) > 10;    -- Target column is VARCHAR(10)

SQL Server "String or Binary Data Would Be Truncated": Fix Msg 8152 & 2628

Quick answer

FAQs

What is the difference between SQL Server Msg 8152 and Msg 2628?

How do I enable verbose truncation messages on SQL Server 2017?

Can I silently truncate text instead of throwing an error?

Does VARCHAR(MAX) prevent truncation errors?

Fix BigQuery "Unrecognized Name" Error: Scoping and Syntax Rules

SQLite "Datatype Mismatch" (Error 20): Type Affinity and Strict Tables

Key takeaways

Enabling verbose truncation diagnostics

Pinpointing the offending row in batch staging tables

Modifying the column safely

Official references

Quick answer

FAQs

What is the difference between SQL Server Msg 8152 and Msg 2628?

How do I enable verbose truncation messages on SQL Server 2017?

Can I silently truncate text instead of throwing an error?

Does VARCHAR(MAX) prevent truncation errors?

Keep reading

Fix BigQuery "Unrecognized Name" Error: Scoping and Syntax Rules

SQLite "Datatype Mismatch" (Error 20): Type Affinity and Strict Tables

Key takeaways

Enabling verbose truncation diagnostics

Pinpointing the offending row in batch staging tables

Modifying the column safely

Related SQL guides

Official references