Teradata Vantage Cloud
Teradata Vantage Cloud is the extensible Cloud Native solution for Cloud Data Warehousing with a focus on data, machine learning, and analytics capabilities for the moder era of data enablement. Vantage Cloud supports many cloud native integration capbilities and its database technology is capable of handling massive transactional and analytical workloads.
- Versions (10 or above) are supported
- Determine which way to connect: Default or SSH Tunneling
- Firewalls on your database server should allow incoming connections through the public internet on your Teradata port (typically 1025 unless customized).
- Be sure to Our IP Grantlist / Whitelist our IP Addresses for cross network database server network access
- Consult with you Teradata administrator as needed on the setup since as a target destination option write access to the targeted database will be required
As a DLH.io will perform loading of data into your Teradata Vantage Cloud instance, write permissions will be requiered to land data into the database in question. These are generic steps to create a user with write permissions to a database in said instance.
- Create a User for DLH.io on Teradata Vantage Cloud
- Connect to the Teradata Vantage Cloud database in question with your admin user in order to create a new user specific to replicating/loading your data CREATE USER <new_username> AS PASSWORD = "tmp!password", PERM=1000000;
- Create a New raw data landing zone Database
- An initial database must be specified in the connector setup to designate where the replicated data will land in your targeted instance.
- Using this or similar best practices logic your Vantage Cloud admin can use the admin user to create a database with generous disk space to support the source data that will be replicated to it, an example would be: CREATE DATABASE DATALAKEHOUSE_RAW FROM "demo_user" AS PERMANENT=2000000000;
- Grant the User Access to the Source Database
- Note: The DLH.io user will need access to create multiple databases for temporary raw data replication. The user should be allowed this access to create new databases as needed.
- Using a direct user GRANT or by creating a role, or other means, provide the new user created above with permissions to read from the source database, for example: GRANT ALL ON <existing_source_database> TO <new_username>;
Remember DLH.io connects to your database instance with credentials supplied by you. We store your credentials securely with our bank-grade protocols.
Click on the Add New Source for Teradata, and in the resulting new source page update the form with your connection information...
Enter your credentials and other information in the fields:
- Enter in the Name/Alias field, the name you'll use within datalakehouse.io to differentiate this connection from others
- Enter in the Target Schema Prefix field, is the prefix of schema(s) that gets created on your destination target connection database for each of the schemas you load in this connection.
- Alphanumeric characters only. It must start and end with a letter but can contain an underscore(_).
- Enter in the Server/Host field, the name of the public server name or the IP Address (most customers use the IP for this field)
- Enter in the Port field, where this database is accessible and the firewall restrictions are open
- Enter in the Database field, the name of the database to connect
- Enter in the Userame/Alias field, the username of user you created in the steps above to give access to DataLakeHouse.io
- Leave Auth Type field alone. It is set to password because DataLakeHouse is using TLS and requires username and password credentials to access the database
- Enter in the Password field, the password for the user you created in the steps above
- Click Save & Test
- This attempt to connect to your database with the credentials provided.
- A message of success or failure will be shown
- If success you'll be prompted with the schema objects objects of the database and will need to complete the final steps for configuration shown below.
- If failure happens with the test connection, the connection is still saved but you will need to correct the failure based on the failure reason information provided in the message
