Errors in rows

• adamcrv

  Hall of Fame

  Points: 3056

  More actions

  August 1, 2007 at 9:56 pm

  #153723

  Hi all,

  This prob real basic answer but i cant figure it out

  i have a package which takes data from an OLEDB source (MSAccess)

  and puts it into the same data structure in SQL 2005, if a record errors then it is redirected to a flat file

  but the package errors out entire sections of rows if one row is incorrect. I have insert commit size to 1000, so it seems all 1000 records dont get committed.

  short of changing the Maximum insert commmit size to 1..how can i effectively let good records go through and bad ones sent to a file?

  maybe it is by design..but just seems like something that shouldnt happen.

  oh yeah dodgy subject name

  sorry !!

  
  ------------------------------
  Life is far too important to be taken seriously

• Crispin Proctor

  SSCoach

  Points: 18161

  More actions

  August 2, 2007 at 2:14 am

  #724092

  Weird, You have it on fast load and a redirect after the destination. This used to give an error as you could not do that. I see now it does not.

  Then what is happening is correct. if one row out of a batch of 1000 fail, they would all get redirected.

  Change your type from Fast Load table to table. This will hurt your insert however as it is inserting one row at a time.

  Rather try curb your errors through better ETL?

  Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!