We are running SQL server 2000 with DTS. We have a stored procedure which worked fine for quite a while. We had to change it recently and since then it fails when being run from a package. it works when run from embaracdero ro sql server enterprise manager, but when run from the package it fails. We backed out the change but it still fails. Here is the response:
Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:String or binary data would be truncated. (Microsoft OLE DB Provider for SQL Server (80040e57): Warning: Null value is eliminated by an aggregate or other SET operation.) (Microsoft OLE DB Provider for SQL Server (80040e57): The statement has been terminated.) (Microsoft OLE DB Provider for SQL Server (80040e57): String or binary data would be truncated.)
Step Error code: 800403FE
Step Error Help File:
Step Error Help Context ID:0

any idea how we fix this?

From http://www.developmentnow.com/g/103_...server-dts.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Were there any table changes? It sounds like one of your columns is
suddenly wider than the package is expecting, which is causing a
truncation error because the destination column is too narrow.

Like Jhofm says, that's the point you have to look into.
It can happen that the same query when run inside query analyzer or
when run inside a dts package gives different result in terms of
failure/success. I faced a similar issue regarding truncation or
implicit/explicit data type conversion.
Check your table's fields and in case post the sql.

Bye
M.