Link to home
Start Free TrialLog in
Avatar of Leo Torres
Leo TorresFlag for United States of America

asked on

Importing Data from TeraData to MS SQL Server ussing SSIS

Where to begin.
I need to Move some data from Teradata to MS SQL ussing SSIS.

Here is the part I am stuck. I order to create the query in Teradata I need to import a file with 20,000 IDs into a Volatile temp table in TeraData then use that table in a join.

CREATE MULTISET VOLATILE TABLE SomeTempTable(
IDs
)
PRIMARY INDEX(IDs)
ON COMMIT PRESERVE ROWS;

--After i create the temp table I need to do this
INSERT INTO SomeTempTable(?)

Open in new window



In SSIS how do i account for the import here because using SQL Assistant i get a explorer window to point to file with IDs.

I am thinking this would have to be done in a script Task. Even using a script task i am not sure how to point to file?

I would like to know how to get this done. If there is another way not involving script task I am all "EARS" as well.

Thank you in advance!!!
ASKER CERTIFIED SOLUTION
Avatar of lcohan
lcohan
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Leo Torres

ASKER

Yes Ideally that would be the way to go but. I don't have access. I do believe I will be granted access either. Its one of those thing you do with what you got sorry. Should have mentioned the access issue from the jump.

I will look into the linked server solution thank you!
Linked server is one option.
How much data you are trying to load from Teradata to SQL Server? Instead of loading the file into Teradata, you can load that into SQL Server and use that to join the Teradata table that is imported using SSIS.
Yea, should have also mentioned that I can not bring in the Teradata into SQL I don't have the resource to bring in all that data. The teradata table has 9 Billion+ rows. Yes 9 Billion! I have managed to pull the bit and pieces i need here and there to put together this data set. But it is inevitable that at some point I had to create a join. The 20,000 IDs are unique IDs I have selected to test a model and do research. Bringing down that table is not an option. :)

I have yet had a chance to explore the Linked server option. Will look into tomorrow.
Yes that's exactly what I ended up doing creating temp tables to import to and extracting flat files for SQL server consumption