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 |
|
kirandevbt08
Starting Member
2 Posts |
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-08-14 : 07:09:53
|
| The error "String or binary data would be truncated" usually happens when you try to insert data into a table and one or more of char/varchar columns are not wide enough to insert the data you are attempting to insert.So my conjecture is that there are some longer than usual strings in your data. That is consistent with what you said - that the jobs were running fine earlier.What does the job do? From the name, it sounds like you are taking a bunch of text files and inserting into a database. If that is so, examine the files to see if there is anything unusual about those. It could be that there are longer than usual strings in them, or it may be that the files are in an incorrect format. |
 |
|
|
kirandevbt08
Starting Member
2 Posts |
Posted - 2012-08-14 : 07:40:17
|
| Hi Sunita,Thank you for your response.But this is not the case, this error message we are not getting while running the SQL Job.This error message is poping up when we rescheduled the job and try to save it.Also when I open the Job --> Properties & click on the Notification Tab the same error message is popping up.Can you please suggest on this.Kiran Kumar N |
|
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-08-14 : 08:10:33
|
| Ah, I misread your original post. The error message is popping up when you try to save the job! I don't know what to look for - hopefully someone else will respond. |
|
|
|
|
|
|
|
|
SQL Error message-8152