- We are getting "String or binary data would be truncated" error when trying to upload our connector file to our compensation db. What is this error and how do we fix it?
- The "String or binary data would be truncated" error (which is specific to SQL Server) indicates that there is data in the upload file that is larger than a field in the table it is loading to. In order to identify the row and column in the upload file that is causing the error, you need to upload the file again with the "Generate a detailed log file?" prompt set to Yes. After the error occurs, the log file will identify the values being inserted into each field of the table for the row that is causing the error. Below is a sample of the information that will be written to the log:
Fri Oct 05 09:37:36 EDT 2007 [ERROR] Values trying to be inserted are:
RCOMP_APPID = [PSL1]
RCOMP_YEAR = 
EMPLID = 
CURRENCY_CD = [USD]
- You will need to identify what value is too big for the field and correct it in the upload file. In the sample above the value being inserted into the RCOMP_APPID field, which is 3 characters, is causing the error.
KBA , LOD-SF-LMS , SuccessFactors Learning , Problem