We are using OLEDB version 184.108.40.206 to connect to Teradata using a .NET 1.1 web application. Basically this application fires a query which produces a result in 2 seconds, format it and display on a farpoint grid control. It was observed that the performance of the application was poor and an indepth analysis showed that the first connection through OLEDB to Teradata took about 40-50 seconds. Is this a problem to be researched at the server where the OLEDB driver is installed or could this be a database issue? Or are there any compatibility issues between .NET 1.1 and OLEDB 220.127.116.11?
We tried to use the same application using a ODBC connection and the connection time to Teradata was less than a second but the query execution time increased marginally by a couple of seconds. Could someone provide any idea as to why this might be happening?
That's a fairly old version. TDOLEDB 1.2 was part of TTU7.1 (released in 2003). And patch level 18.104.22.168 in particular was compiled with a pre-release version of TeraGSS. You don't say what version of ODBC you're comparing against.
I'd suggest you install a newer driver; remember that newer versions will also require compatible TDICU and TeraGSS. In particular, make sure you have a version of TeraGSS that includes the performance fix for encrypted logons (DR101738), e.g. TeraGSS 22.214.171.124 or later with TDOLEDB 1.3 or TeraGSS 126.96.36.199 or later with TDOLEDB 1.4.
We are also having some issues with OLEDB. Our environment is Net 2.0, Visual Studio 2005 and Teradata OLEDB 188.8.131.52, we have also attempted to use the NET data provider 184.108.40.206.
With the OLEDB release with VS2005 we do not see the (Views) for a connection and the (Stored Procedures) show no SP's even though there are SP's. Our baseline control is to use the generic OLEDB provider in VS2005 with Teradata ODBC DSN which works fine with (Views) and (SP's). However we have seen initial conncetion times of 20+ seconds which we initially thought might be network related.
The NET provider is giving us a BadMoveMode(387) error from the CLIV2. Also the NET provider does not appear in the VS2005 list of providers when trying to define a connection using the wizard.
Current configuration is ODBC 220.127.116.11 GSS 18.104.22.168 CLIV2 22.214.171.124 ICU 126.96.36.199 OLEDB 188.8.131.52 NETDP 184.108.40.206
In a recent post we have seen that a GSS ver 220.127.116.11 is recommended. We have not been able to locate that update.
Anyone using OLEDB with VS2005? Anyone using NET DP with VS2005? What combination and version of components are being used?