May 3, 2007 at 9:47 am
i've found this problem before where if a table didn't exist at the destination SSIS would error out instead of creating it.
now i created it from script but i want to drop the table first and then have it create it and copy the data. Destination is sql 2005 SP2 and the source is sql 2000 SP4.
I created it using copy sql objects task to copy 4 tables from a database. I need to drop the destination objects first since they always add columns, etc and i don't want to make changes on the destination manually. It keeps failing and it looks like the destination objects aren't being dropped and the failure is due to differences in the schema.
May 4, 2007 at 1:20 pm
I think you need to recreate the package every time they change the table structure. From what I've seen it looks like SSIS stores the table definition at the time the package is created. If the underlying table structure changes then package will be out of sync.
May 7, 2007 at 10:46 am
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply