IGNORE : 8152 16 String or binary data would be truncated. ? 1

[myvision69]

Is there a way to ignore "Message 8152 16 String or binary data would be truncated." so that the Update or Insert is successful even though string value is being truncated.

 

[gmmastros]

You get that error when you try to insert too much data in to a field that cannot hold that much.

declare @Temp Table(Data varchar(2))

[green]-- This one errors[/green]
Insert Into @Temp Values('This is too long.') 

[green]-- This one is fine[/green]
Insert Into @Temp Values([!]Left([/!]'This is too long.'[!], 2)[/!])

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[myvision69]

Thanks for the quick response.

I was hoping that I do not have to code each column with Left(). Is there a way to disable so it automatically takes only the part of the string that fits in the column width.

 

[SQLDenis]

>>I was hoping that I do not have to code each column with Left(). Is there a way to disable so it automatically takes only the part of the string that fits in the column width.

restrict on the input side and use stored procedures with parameters that are the same size as the columns

Denis The SQL Menace
SQL blog:

http://sqlservercode.blogspot.com/

Personal Blog:

http://otherthingsnow.blogspot.com/

 

[ESquared]

create table blah (a varchar(1))
insert blah select 'ab'
select * from blah
set ansi_warnings off
insert blah select 'ab'
select * from blah
set ansi_warnings on
drop table blah