DTS Error Logging
Posted on 2011-03-23
Recently we received an error using one of our scheduled DTS packages. The problem was due to bad data, however the error logging is extremely generic and it took me quite a while to find the specific row that contained the bad data. I reran the step and was able to determine that the problem occurred after the 39000th record and before the 40000th record, but that's the best I could get. I removed that record, and everything ran fine.
My question is, is there a way to make the error logging more specific?
Do you know of any way to identify the record causing failure in a better way? If that's not possible, is there a way we can set the record number display to be less than 1000? Something like 100 might make it easier to narrow down an offending record. 50 or 25 would be even better.
Thanks in advance.