Job Design:
Seq File --> xfm1 --> SQL Server #Temp table --> select distinct --> xmf2 --> SQL Server final table
I need to do a bunch of lookups in xfm1, where the lookups will map source data to different values (example effective date to month surrogate key). I then need to write the distinct rows to the final table.
A great case for a transient, temporary SQL Server table. Alas, since DS does not persist the connection to SQL Server, the temp table is gone when xfm2 kicks in.
Is there any way to get DS to not drop the initial SQL Server connection so I can use temporary tables?
Thanks,
Scott
Can I use a SQL Server #Temp table in another transformation
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes.
In fact, if you want the entire composite key, it's easier and faster. The system variable @ID accesses the entire composite key. However, this is necessarily unique anyway - it's the primary key.
In fact, if you want the entire composite key, it's easier and faster. The system variable @ID accesses the entire composite key. However, this is necessarily unique anyway - it's the primary key.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.