Yep, it makes sense. I'm not sure if that's how I'd design it, but it is what it is. My personal preference would be to have a Customers...

Yes, and you are right that it sounds like that is already what is happening with meichner's existing Customer Address table. The Customer Address should only be related to...

That's fair. I think we need more info then from the OP as to how the addresses are currently being related to other entities.

meichner,

Care to handle this? ...

Ok, so the proper way to represent the many-to-many relationship between Customers and Addresses is to have the associative table CustomersAddresses. Agreed. But you do not want to...

Using the CustomerAddress table is the correct way to go if you truely have a many-to-many relationship between Customers and Addresses, but using the CustomerAddressID to 'link' that value to...

You usually see this error when the destination is not on the same server as the SSIS instance. In your case, everything is on the same node. I...

That, or setting the Error options in each of your Destination objects to ignore the error or redirect the error rows to another table.

Each item inside a container will be part of the same transaction. If you want to allow one table's data to load if another table's load fails, they need...

Nope. In your case, the Data Flow task is the lowest grain container available to you. You'll notice that while inside the Data Flow task, there are no...

I would go with a combination of the above suggestions. First, design your packages with the appropriate transaction behavior to meet your needs. Then, use a lookup transformation...

If all 10 data pumps are inside of the same Data Flow task, it will be an all or nothing load since everything inside of that Data Flow task will...

Have you tried using the Transfer SQL Server Objects transformation?

Agreed....we don't have enough info to help you here. How about posting the code that you are using to 'mark' the row as reserved. It looks to me...

What are you trying to do here? I agree that such a simple statement as SELECT 1 should work here, but I fail to understand what your desired end...

Select your Destination Flat File connection in the connection manager, press F4 to pull up the object properties, and use the Expressions feature to set the Connection String property of...