Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JeffT
Posting Yak Master
111 Posts |
 Posted - 2008-09-04 : 09:08:42
|
| Hi,We are converting from SQL Server 2000 to 2005. In one of our batch files, we run a stored procedure via isql. We switched the isql to SQLCMD and discovered that isql was more "forgiving" with a "String or binary data would be truncated" issue that SQLCMD flagged. The value (coming from the mainframe) in one of the variable fields in the stored procedure was too large for the table field (45 bytes vs 35 bytes). isql automatically truncated the data in the variable field to 35 and completed successfully. I know that the obvious solution here is to do a "left(variablefield,35)" or decrease the size of the input mainframe file field but, that aside, is there any way to "tell" SQLCMD to automatically truncate the data as isql did ? We're trying to make as few stored procedure coding changes as possible.Thanks!Jeff |
|
|
JeffT
Posting Yak Master
111 Posts |
Posted - 2008-09-04 : 09:24:30
|
| Btw, the data that is truncating is NOT an issue for us...Jeff |
 |
|
|
|
|
|
SQLCMD in Sql Server 2005