Comments on: Dynamic table loading in SSIS (Part 1)

by: Protean

Wed, 16 Jul 2008 09:56:21 +0000

Dynamic table loading in SSIS (Part 2)

I talked in a previous post about the possibility of using the format command and bulk insert task inside of a foreach loop in order to load all your tables in a single batch… I don’t much like the method as it means you have t…

by: FB

Wed, 20 Feb 2008 22:40:35 +0000

You’re right. You couldn’t do this from one database to another… however it could be achieved if you absolutely had to have that ability in a single package, by executing a process task which runs the export utility in the source system, then loading the files using bulk insert… but having said this, it sort of defeats the purpose of integration services in that you can’t transform any of the data, and that you can’t load it in a single pass. Also, the dataflow is faster than bulk insert so you’re losing out in performance too!! So after all that there would be no point using SSIS!

I used to use this method in a datawarehouse I worked on where all our source databases dropped csv files on to a central repository, and from there I would call a single SSIS package passing in the tablename to get the data loaded into a staging area. From there it required 100+ packages for the transforms.

In the end there is no way around it!!

by: Valek

Wed, 20 Feb 2008 22:00:26 +0000

I see this is a solution file->database. Now how do we implement database 1->database 2 in a similar way? I guess in this case we need to write alot of custom code.

by: FB

Wed, 20 Feb 2008 15:42:59 +0000

I’d just like to add to this that bulk insert task in SSIS does have various limitations especially in regard to permissions and file locations. Also, its probably worth mentioning although I’m sure you all know this, that you can’t transform the data in any way. However, it will allow you to accomplish a simple import of data if that’s what you are trying to do.

Cheers