Community Edition is a SUSE Linux Enterprise Server (SLES) operating system and Teradata Database packaged into a virtual container that runs in a VMware vSphere ESXI virtualized environment on third-party hardware. Community Edition software consists of a template and associated property files and scripts. When a Community Edition virtual machine is deployed, it operates as a fully functional instance of the configured Teradata Database. Once deployed by the VMware administrator, Community Edition can be used to evaluate Teradata Virtual Machine and the Teradata Database.
Note: You must have administrative privileges on the destination VMware environment to install and configure Community Edition virtual machines.
The following instructions should help you set up and configure the Teradata SQL H capability with your Hadoop instance. First, however, you need to download and start up a Teradata Express image with the SQL H Connector installed. On the Teradata Express for VMware Player, download on of the following two versions.
Teradata Express 15.0 is now available so that you can evaluate the new features of Teradata. Teradata Database 15.0 is the newest release of Teradata’s industry-leading RDBMS. This release extends Teradata’s leadership in several key areas, and continues to position Teradata Database as the database of choice for Integrated Warehousing, Business Analytics, and participation in the Unified Data Architecture.
This article provides a high-level overview of the process involved in moving to Teradata 13. Teradata 13 offers many new features and some of the highlights are covered in other articles on DEV/X. The focus here is how to get to Teradata 13.0.
The purpose of the new Teradata 13.0 feature that allows you to create tables with no primary index is improved performance of FastLoad and Teradata Parallel Data Pump Array INSERT data loading operations.
Middle-tier applications may stand between end-users and Teradata Database; accepting requests from users, constructing queries from those requests, passing the queries to the database, and then returning results to the users. The middle-tier application logs on to the database, is authenticated as a permanent database user, and establishishes a connection pool. The application then authenticates the individual application end-users, some of whom may request access to the database through the connection pool.