Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I read couple of online documents to get start with the Teradata basics.
I am curious to know what is full client version of Teradata client software to install on Windows/unix/Linux environments? What is best suited for client install?
I see different client versions depends on the type drivers/applications
1. Teradata JDBC
2. Teradata ODBC
3. Teradata dot net provider
4. Teradata SQl assist/BTSE
5. Teradata Express
6. Teradata OLE DB provider
7. TTU .... etc
To more clarity on my Question .. DB2 and Oracle have a full client software which can install locally on windows/unix systems and it will be able to use or all type connectivity(odbc,jdbc,ole db,ado .net...etc)
Typical base toolset for end users/developers submitting ad hoc queries from each environment:
Windows (TTU 13.10 Client Install - 400MB)
Teradata SQL Assistant
Teradata .Net Provider and/or ODBC Driver
Teradata GSS & ICU Libraries
(Optional) WinBTEQ
(Optional) Teradata CLI - for WinBTEQ
Linux/UNIX/Mac OS X
Teradata JDBC Driver
Teradata Studio Express
(Optional - if using Eclipse)Teradata Plug-in for Eclipse
Many of these components can be found in the Teradata Developer's Exchange Downloads section. Starting with Teradata 12 they have reset the version numbers in an attempt to address the confusion with the different development life cycles of each component contained within their Tools and Utilities. Tools for Teradata 13.x should be compatible with Teradata 12 and Teradata 14. However, certain features specific to a given database release may not be available unless you are using a version of the client that is equal to or greater than the database version.
For ETL Development, then you will be relying upon the BTEQ, FastLoad, FastExport, MultiLoad combined with the Teradata CLI to connect to Teradata.
This answer is for Windows only.
To run queries against a Teradata database, you need the following:
Teradata SQL Assistant
Teradata .NET Data provider
Teradata ODBC Driver
To know, if your system has Teradata ODBC Driver, goto Control Panel, Administrative Tools -> Data Sources -> Add and see if Teradata is listed.
Sample screenshot below:
If you are working on new database and ( if you have license to use ), you can have a look at Teradata parallel transporter. It provides extract-load capabilities with configurable scripts.
Related
I am configuring several Windows 10 systems that will need to reliably connect via ODBC using system DSNs to both Progress version 9.x and Progress version 10.x databases.
I have been told by one of our IT staff that interfacing with Progress versions 9.x servers require the OpenLink ODBC client software, while interfacing with Progress 10.x requires the OpenEdge ODBC client software.
I am not completely confident that this is true, but I have not been able to find any authoritative documentation citing version compatibilities between these technologies/products. Can someone please direct me to information about the compatibility between these products, pertaining specifically to versions of these products?
It was version 8 that required OpenLink.
Version 9 is unspeakably ancient and version 10 not much better. The current release is OpenEdge 12. ODBC options for v9 should include Progress/Datadirect ODBC since the SQL-92 engine was introduced in that timeframe. Documentation for such things is going to be very, very sparse.
Progress' current ODBC documentation: https://www.progress.com/odbc/openedge might get you started though.
OpenLink does also support v9 and they have some documentation here: http://wikis.openlinksw.com/UdaWikiWeb/MigratingFromSQL89ToProgress10SQL92Connectivity
In the Progress 9 windows client, there is a 32bit ODBC driver for Progress 9. However, if the program you are trying to connect to Progress from is 64 bit, this will not work directly.
We have succeeded in using an old 32bit version of SQL Server as a tunnel, creating SQL Server views on the Progress database and querying these views using a SQL Server ODBC driver from the 64 bit program.
It's messy and awkward, and I wouldn't want to vouch for the robustness of such a solution, but if this is only a stopgap then perhaps it may help.
OpenLink provide Progress SQL-92 ODBC Driver for version 9.x, 10.x & 11.x and can provide such connectivity to both 32 & 64 bit Windows applications, see http://wikis.openlinksw.com/UdaWikiWeb/InstallProgress92LiteWin32 ...
I am here again, now asking for help with something else. Now my problem is that I have connected a SQlite 3 database with ODBC but i do not know how to read and take out information from it.
Looking in youtube tutorials I reached the Management studio for Microsoft SQL Server, but I do not believe this program could help me out.
You first need to install a SQLite ODBC Driver on your target machine. Then you have to go into your administration tools and add the proper database.
See the link below for a detailed tutorial.
https://faimsproject.atlassian.net/wiki/spaces/MobileUser/pages/81595619/How+to+connect+to+an+SQlite3+database+with+Access+as+a+frontend
Are there alternatives to Teradata SQL Assistant {on windows}, possibly freeware?
Heidi is great but it does not support Teradata.
What are the pros and cons of the alternatives?
Teradata Studio and Studio Express are the long term replacements for SQL Assistant from Teradata. They are developed around an Eclipse based IDE and are available to download from Teradata Developer Exchange.
Database .NET is a Free universal database manager for Windows All,
It supports most popular databases, including Teradata database.
Not sure if the reason is price, but the latest version of SQL Assistant is downloadable free from Teradata's website:
http://downloads.teradata.com/download/tools/teradata-studio
You don't have to install everything, just pick and choose what you want.
Current desktop application is developed using PowerBuilder version 9 with Oracle 9.2 as a back end. Now I need to migrate the back end Oracle to 11.2.0.2. From Googling I found PowerBuilder 9 is no longer supported. Is it possible to connect to Oracle 11.2.0.2 with PB 9? Kindly let me know if I can migrate the same application to higher version of PB like PB 11?
If you look at this response from Terry Dykstra you'll see your options under PB9 are:
the O90 driver, ODBC, OLEDB or JDBC
As for migrating to a higher version, migrating to higher versions of PB are typically comparatively small efforts (but no guarantees), assuming you have all the source code.
You mention upgrading to PB11. Keep in mind that PB11 also is no longer supported. Sybase (now an SAP company) typically supports current and previous major versions (with some overlap), so right now that means 12.5 and 12.0.
Good luck,
(another) Terry
Few months back I saw TeraData Express Edition. I have no idea of this beast. I want to know whether it still comes with Express Edition and whether it is a good idea to use this database for Windows based mid-sized apps.
It really depends on what you want to do with this application. From an application perspective, a great weakness of Teradata is that it does not support read committed transaction isolation. If you are attempting to use Teradata as an OLTP database, then you might want to try something else. If you are using it to crunch numbers, then yes, go with it. The one issue is that Teradata Express Edition is not supported that well. Express edition is essentially a snapshot of the database for a certain release. If you find and report a bug, it will take a long time for you to receive a fix. Teradata only releases the express editions once per db release. However (imo), if you buy the real version, you will receive a pretty quick patch which will be rolled into the database software.
I use teradata in my technical support work. I work on database middleware, and Teradata is one of our supported data stores. Define mid-sized? 1-200 transactions per second? I'd stand ANY commonly used database up against that. 10000 tps? Maybe not - maybe you go to the enterprise edition.