Hi,

We're trying to build a new datawarehouse using SSIS. We've addressed
several entities that we need to load.
A lot of these have to go through exactly the same steps. So i would
like to build a generic SSIS package and use a variable for each entity
that I need to load. I've noticed that this will not be a problem for
the Source and Destination in my data flow, since I have the option to
use a variable as a table name. However, this doesn't work for lookups,
I seem to have point to a specific table, and seem to have no options
to use package variables here.

As far as I can see now, this is the final hurdle; if I can use a
variable as a tablename (or even in the lookup SQL statement), I only
need very few IS packages. Otherwise, I will need to copy them about 15
times just to fill in the lookup table...

Could anyone please help me out?

Thanks in advance,

Pipo

Hello Pipo,

When you say that it will not be a problem using variables for the source
and the destination tables and that you want to use this to make a generic
package I am intrigued.

Is the metadata the same for all these tables? if it is then no issues else
I think you are going to have problems.

As for the Lookup. I know of no way to dynamically construct the lookup
transform.




Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

On this part of the load process the metadata is the same for all
tables; they only contain the columns Source, SourceID, DerivedID.
Purpose of these table is to give persons from different sources the
same derived key, when they are in fact one.

Pipo



Allan Mitchell schreef: