I tried to create a job containing only one step. In the first time, the T-SQL script is like this:
The job was manually triggered and scheduled to run. It run successfully. In the second time, the script to run is like following:
This time, the job can not be run manually or scheduled.
The error log shows me following message:
Executed as user: sa. String or binary data would be truncated. [SQLSTATE 22001] (Error 8152) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
It seems like my script is too long. Is there any max length I should consider here? Did anybody experience similar problem before?
By the way, I'm using SQL 2K with SP3.
Thanks for your help!
Frank
Code:
select count(1) from transaction
Code:
use int
go
update transaction
set name = 'good',
addr1 = 'first',
transDate = null
where invalid = 0
go
delete from transaction
where tranDate between '1/1/2002' and '2/1/2002'
go
The error log shows me following message:
Executed as user: sa. String or binary data would be truncated. [SQLSTATE 22001] (Error 8152) The statement has been terminated. [SQLSTATE 01000] (Error 3621). The step failed.
It seems like my script is too long. Is there any max length I should consider here? Did anybody experience similar problem before?
By the way, I'm using SQL 2K with SP3.
Thanks for your help!
Frank