Check out the solution in the video TSQL: "String or Binary Data Would Be Truncated" Quick Solution. As you can see, we learn one possible solution to the string or binary data when the data involve VARCHARs/CHARs/etc. It should be of note that we should create another table only if space allows.
Some examples we see in the video:
- When we see this with large inserts?
- What do we do when we have more than hundreds of columns?
- Where could we look that would mislead us?
Check out the highest-rated Automating ETL course on Udemy, if you're interested in data.
When I mentioned VARCHAR columns, I meant string. We generally see this error with string-based columns, though we will sometimes see it with binary. This error ultimately shows up because we're not following the schema of our table (or vice versa). We can either trim the data or re-create the table with a new schema that matches our data.