tag:blogger.com,1999:blog-8413638223026049990.post7197218148228710453..comments2023-01-11T04:09:04.172-05:00Comments on <center></center>: SSIS 2008 / SQL Server 2008 Connectivity IssueBob Pearsonhttp://www.blogger.com/profile/16528166535649336177noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-8413638223026049990.post-89800651577508063012012-02-04T11:09:06.619-05:002012-02-04T11:09:06.619-05:00This idea worked like a charm for me. I'm load...This idea worked like a charm for me. I'm loading data without staging the raw data first. On the way to my target table, I want to check for dirty incoming data and save those raw records in an error table. I ended up with 1 OLE destination for my target table, and a few destinations for the error table, all using the same connection. With a smaller number of records, I had no errors, but with larger numbers, I'd error out usually after a few million rows.<br /><br />I redesigned this so that I have two connections pointing to the same database. For the errors, I gathered them all up in a union before sending them to the error table. This way I have only 2 destinations, each with its own connection. All of my problems went away. Thanks for the tip!djhubajubehttps://www.blogger.com/profile/02401869660718918691noreply@blogger.com