November 9, 2009 at 1:08 pm
can anybody suggest if i can use execute sql task to teradata database if so what type of connection should i use?
I should also pass the sql with a parameter to teradata database
November 9, 2009 at 2:13 pm
You can use an ODBC connection with an Execute SQL task to query Teradata from SSIS. Treat it like any other connection and put your SQL statement in the SQLStatement property of the task.
November 9, 2009 at 3:17 pm
can you please explain in detail if it is just ODBC or teradata ODBC?
can i send paramter in my sql query?
November 9, 2009 at 3:31 pm
Well, when I say ODBC, I do mean the Teradata provider. I'm using TDATA32.DLL from NCR Corp. This should be the default Teradata ODBC connection that gets installed with your Teradata client (SQL Assistant).
There's also a .Net Teradata provider available. I use both. There seems to be some quarks with how the .Net connection works so I have a combination of both on one of my packages. I use the ODBC connection for SQL calls from the Control Flow (ExecuteSQL tasks) and the .Net connection for use with DataReader source adapters within my data flows.
Don't forget that you can dynamically build out Teradata BTEQ, IMPORT, or Fast Export scripts and call them from SSIS!
As far as the parameters so, yes, just like any other ExecuteSQL command, you can use parameters. Here's a link to show you how to use parameters w/ the ExecuteSQL task:http://www.sqlis.com/post/The-Execute-SQL-Task.aspx
November 9, 2009 at 7:44 pm
i tried to use ado .net with the teradata and used select statement and when i click on parse query i get
"Object reference not set to an instance of an object."
if i continue to execute with ignoring the above error i get the below error
failed with the following error: "Object reference not set to an instance of an object.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Any Help
November 10, 2009 at 9:16 am
I assume you are using the ExecuteSQL task? I get the same thing with the .Net connection and the ExecuteSQL task. Try the ODBC connectoin and see what you get. That one works fine for me.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply