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 |
scottjohniec
Starting Member
7 Posts |
Posted - 2006-08-26 : 11:34:02
|
I'm about ready to tear my hair out :-) I'm working on projects that require me to download LARGE Demographic Files from an AS400 to our SQL Server. These files contain Birthdates, Arrest Dates, Booking Dates, etc.. For whatever reason, they weren't edited for Leap Year, valid Months, Days or Years. I've been changing all the fields on the SQL Tables from DateTime type fields to varchar and letting them pass through the DTS since the package is VERY sensitive to Dates Fields to put it mildly. I then run commands to check the fields and notify the End Users to clean up the Data. Now My Question... Is there a way in my DTS Package to know what record it's erroring out on? I've tried everything my limited knowledge knows. I've installed all the error logs that the books suggest but that only shows where the program bombs out. My BARBER will greatly THANK YOU for some direction. I know that 02/29/01 wasn't a Leap Year and 45/23/06 isn't a valid Arrest Date :-) DTS also knows but it's not talking! |
|
Rishi Maini SQL2K5 Admin
Yak Posting Veteran
80 Posts |
Posted - 2006-08-27 : 09:42:04
|
Hi,You can go to "Options" Tag in your "Transformation".Under "Options" you will see "Exception File" ( Give a path of the file where you want your bad rows to be redirected)Check "Source Error row" Select the appropriate "Max Error Count" value and you are done. The package will still show a failed status but it will filter out all the bad rows in this "Exception File" which you can open with any Text Editor.ThanksRishi |
|
|
scottjohniec
Starting Member
7 Posts |
Posted - 2006-09-01 : 09:37:19
|
Thanks Rishi !!I'll give it a try... I'm assuming it will be 1 transaction at a time and not the total number of errors. |
|
|
|
|
|