MSSQL Sorting or binary data would be truncated

From support-works
Revision as of 11:42, 14 February 2018 by Pamelal (talk | contribs) (Created page with "{{Template:Basic Cover |title=MSSQL Sorting or binary data would be truncated |type=FAQ |htl=Y }} {{Template:Basic Status |status=Published |version=1.0 |authors=HTL QA |appl...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search



Status: Published
Version: 1.0
Authors: HTL QA
Applies to: any Supportworks ESP Version

Error on extended table when logging an Incident or Service Request. The call still gets logged but the call details form has some fields missing information.

Open the log and check the Insert statement that is failing. It will have: 

[Microsoft][ODBC SQL Server Driver][SQL Server] String or binary data would be truncated.

It means there is a field in the extended table that you are attempting to populate that is not large enough for the amount of data you are sending to it. For example, table extoc_cfh has varchar 12 but you are trying to enter 'reset your password' into that field which is 19 characters long.

Retrieved from ‘https://wiki.support-works.com/index.php?title=MSSQL_Sorting_or_binary_data_would_be_truncated&oldid=1245’