November 3, 2009 at 10:15 am
Hi
I've been slogging away for a few days now and have hit a brick wall.
Using SSIS 2005, I need a way to move a table from one database to another, including data. The problem is, there are 400 potential tables, and I don't know which one it will be until runtime.
Basically the tables are datasets, and they vary in table definition and data volumes. The code is required to move certain of these dataset tables to a new copy of the database on a different server, for demos, testing, etc.
But the tables required will vary from copy to copy, and so I'm looking for a way to parse the table at run-time.
I've tried SQL Server Objects Transfer, and it leaves out the defaults,etc.
Dont want to create data flow for each possible table as more are added all the time.
Trying to find a way to do it in a script task maybe, even using script to create a new package / task programmatically.
any ideas?
Thanks guys n gals.
Barri
November 3, 2009 at 10:50 am
Not having had to do this, it does look like you may need to build the transfer package dynamically. I'd be interested in seeing how you accomplish this task.
November 16, 2009 at 10:14 pm
I was just looking at this, it looks like the copy objects will copy defaults..
Anything else you noticed it was missing?
I was thinking also that the only way to make it dynamic otherwise was to dynamically build a package for it..
CEWII
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply