All Forums Connectivity
marcmc 112 posts Joined 12/05
03 Jan 2007
Add Teradata .net ADO reference to project

Hi all,I am helping migrate a datawarehouse from SQLServer to Teradata. As part of this one .net application has to be rewritten to connect to the new teradata datawarehouse.However, I am not able to add the Teradata .net driver as a reference in the .net Project.I am using the Microsoft .Net framework version 2.0 and have installed the .Net driver for Teradata provided on this website. What do i need to do to reference the TDOLEDB on the local machine?Any help truly appreciated.Marc.

NetFx 346 posts Joined 09/06
03 Jan 2007

Is you question in reference to the "OLE DB Provider for Teradata" (a.k.a. TDOLEDB)?The .NET Data Provider for Teradata (not TDOLEDB) installation adds a registry entry to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders. Visual Studio 2005 reads the registry key and displays the Assemblies in "Add Reference" dialog box.Are you using Visual Studio 2005?

marcmc 112 posts Joined 12/05
04 Jan 2007

Hi,I am running windows2k prof.I have MS Visual Studio 2003 V7.0.I have systematically installed the below in the following order as specified in the release notes.1. tdicu.01.01.01.02 setup.exe2. TeraGSS.06.01.00.14 setup.exe3. cliv2.04.08.01.04 setup.exe4. tdnetdp.01.01.00.00.exeI am expecting that the library(.dll) will show up in the COM tab of the Add Reference dialog of the .net project but it does not! I cannot understand what I have done incorrectly.Thankyou for any response.Marc.

marcmc 112 posts Joined 12/05
04 Jan 2007

I had no joy with this and so decided to change to use the Microsoft.Data.ODBC Classes. These have worked. I am wondering about the connection strings of these classes an whether they can take parameters? For example, the 1st statement below works but the 2nd falls over (even though the parameters been passed in the 2nd Stmt are identical to the hardcoded values.) with an exception as follows:Microsoft.Data.Odbc.OdbcException' occurred in microsoft.data.odbc.dll. Additional information: System error.'TDODBCcnString = "DSN=smp001;UID=dbadmin;Pwd=dbadmin;"TDODBCcnString = "DSN=ServerLogXML;UID=UNameLogXML;Pwd=PasswordLogXML;"For anyone who has integrated Teradata to .net and has used these classes, can you help clarify. My application is designed to be portable and move between server environments therefore this must be able to work!

marcmc 112 posts Joined 12/05
04 Jan 2007

for anyone interested, i forgot to build up the string with concatenations. D'ohTDODBCcnString = "DSN=" & ServerLogXML & ";UID=" & UNameLogXML & ";Pwd=" & PasswordLogXML

NetFx 346 posts Joined 09/06
04 Jan 2007

.NET Data Provider for Teradata requires .NET Framework 2.0 and is certified with Visual Studio 2005. .NET Data Provider for Teradata is not a COM object and will not show up in the COM tab. It shows up in the .NET tab in Visual Studio 2005.

marcmc 112 posts Joined 12/05
04 Jan 2007

Thanks.Maybe it's my use of MS Visual Studio 2003 v7.0 then.Is there a .NET data provider for 2003 v7.0 as ODBC seems quite slow.Thanks again.

NetFx 346 posts Joined 09/06
04 Jan 2007

Will your application target .NET Framework 1.1 or .NET Framework 2.0?.NET Data Provider for Teradata requires .NET Framework 2.0. It implements abstract classes in System.Data.Common (e.g. DbConnection) namespace which are part of the .NET Framework 2.0.Visual Studio 2003 targets and uses .NET Framework 1.1.

marcmc 112 posts Joined 12/05
05 Jan 2007

Hey,I installed .NET Framework 2.0 because the .NET Data Provider for Teradata had it as pre-requisite.My applications still work so I can only assume that I am still pointing at 1.1 because I use 2003 V7.0.How can I know/find out this?Also, I have extensive use of DataSets, dataAdaptors etc in my Apps.Will Microsft.Data.Odbc utilise these under 2003 V7.0?Thanks for the replies.Marc

NetFx 346 posts Joined 09/06
05 Jan 2007

CorFlags.exe is a new utility in .NET Framework 2.0 SDK.It can be used as a dignostic tool; it displays the CLR Header version of the Assembly (.exe or .dll). CLR Header 2.0 indicates .NET Framework 1.0/1.1.CLR Header 2.5 indicates .NET Framework 2.0.For example:C>corflags C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\system.data.dllMicrosoft (R) .NET Framework CorFlags Conversion Tool. Version 2.0.50727.42Copyright (c) Microsoft Corporation. All rights reserved.Version : v2.0.50727CLR Header: 2.5PE : PE32CorFlags : 24ILONLY : 032BIT : 0Signed : 1C>corflags C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.data.dllMicrosoft (R) .NET Framework CorFlags Conversion Tool. Version 2.0.50727.42Copyright (c) Microsoft Corporation. All rights reserved.Version : v1.1.4322CLR Header: 2.0PE : PE32CorFlags : 9ILONLY : 132BIT : 0Signed : 1I cannot answer you question about the .NET Data Provider for ODBC.

You must sign in to leave a comment.