Integration Services and Teradata as source

Hi All,

Please let me know whether we can use Teradata as Source in SSIS (Target is SQL Server 2005). ie. Do we have oledb driver for NCR Teradata to connect to it. Our SSIS will be hosted in 64 bit SQL, but for development we use 32 bit.

Any inputs is really appreciated.

Regards, kart

NCR provide an OLE-DB provider, so I would guess that would be your first option. Saying that I do not know if it supported within SSIS, not all providers are, you need a minimum set of features to be implemented in the provider, and implemented correctly according to the specification. Give it a try.

ETI also produce a SSIS connector for Teradata which may be worth a look-

ETI - High Performance Data Integration
(http://www.eti.com/microsoft/)

|||

There are various ways to conneto to Teradata. Their OleDB provider supports both 32 and 64 bit. They also have a new .NET provider, though I'm not sure how good it works with SSIS.

iWay has also Teradata providers (OleDB, ODBC) which could be used.

One thing to note here is that Teradata providers do not support Commands, though they support tables and views. As a workaround, some of our users use linked server in SQL 2005 and got the Commands working that way.

You can also check our young but improving connectivity portal for Teradata and other data sources : http://ssis.wiki.com/Data_Sources

|||

HI Deniz and Daren,

Thanks for the info.

It would be helpful to me if you could provide some inputs on Cost Factor w.r.t ETI and iWay and any other implementation details. I assume, using ETI/iWay connectors is a better approach than using OLEDB Driver provided by NCR - as these improve the access performance.

Regards

Kart

|||

Kart, I think it would be better if you did the research. I don’t know your business requirements, technical constraints, your budget, or quantities you would require, all of which may effect the cost and eventual product selection process. Talk to the suppliers and find out what they can do for you.

|||

We am trying to use the OLEDB provider from Teradata for SSIS and running into the following issues

We are able to connect to the Teradata database using the drivers. When we use the import wizard, the authentication screen into Teradata takes about 5 minutes to return. The screen that brings back the list of tables in Teradata to select from takes about half an hour to come back. The screen after that for mappings also takes a very long time to come back.

So, as you can see, every action on the wizard is taking way too long to come back and we are unable to complete the most basic package creation. We tried to manually create the package as well without using the wizard. Even that takes a long time to come back with the list of tables to select from.

Are there any such known issues with using the Teradata drivers with SSIS. This is making development impossible with Teradata OLEDB Drivers.