Three databases that were forced restored now do nor allow manual entry, even one single character, although using an update statement works. This is not a matter of changing the length of the datatype, but something else. For the life of me, I can't figure out why this mere attempt at manual data entry generates the error below:
"No row was updated.
The data is row 2 was not committed.
Error Source: >Net SqlClient Data Provider.
Error Message: String or binary data would be truncated.
The statement has been terminated.
Correct the errors and retry or press ESC to changes the change(s).
Why does this message speak about truncating when only one character is entered?
We are using SQL Server 2005 SP 2
December 5, 2008 6:23 PM
December 6, 2008 1:33 AM