Archives of the TeradataForum
Message Posted: Wed, 05 Dec 2001 @ 18:24:49 GMT
I am a recently RIF'd 13 year Teradata SE veteran who has heard this problem many times, but I can tell you this, CLI and ODBC are not going to differ in logon/data transfer speeds. I would suggest the following:
1. Double check your TCP/IP address and make sure it is a valid address to a Teradata node running the Teradata database software. You never know when your hardware people change things around.
2. Make sure your are not getting "lost" in your companies DNS system if they use this feature. That means "Domain Name Services" I believe.
3. Double check how you have defined this ODBC connection thru your ODBC setup software. Many many people don't know how to do this correctly. I would suggest to find someone who has a good working version of ODBC and see how they have done it. It's too hard to describe how to do it with all the different flavors of windows out there, they are all just slightly different.
4. I always download the shareware 'InTeragate' software and set it up with both an ODBC and CLI connection to test out both interfaces before I try to get other software packages to use an ODBC connection. This has saved me a lot of time thru the years.
The newer versions of ODBC can now do multi-statement requests because of all the new data-mining features that were added into V2R3 and beyond, so there really isn't a good reason to use CLI unless you want to run ML,FL, FE or Tpump from your host system. Many of the 3rd party software packages ONLY use an ODBC interface anyway, so don't waste your time with CLI unless you really need to use it.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|