website logo
⌘K
Getting Started 🚀
What is DataLakeHouse.io?
Our Business-Value Focus
Learn the Basic Concepts
Connectors
Operations Applications
Asana
Aloha POS
Baremetrics
Beans Route
BILL
Bloom Growth
Bullhorn
Calendly
Ceridian Dayforce
ClinicalTrials.gov
ConnectWise
DBT Cloud
DBT Cloud Log Stream
Facebook Ads
Food Delivery Service Connector
Google Analytics 4
Google Play
Harvest
Hubspot
Jira
MailChimp
McLeod Transportation
Microsoft Teams
NetSuite (Oracle NetSuite)
NetSuite SuiteAnalytics
Optimum HRIS
QuickBooks Online
Salesforce
Salesloft
Shift4 Payments
Shopify
Square
Square Marketplace
Stripe
Toast
TriNet
Verizon Wireless Business
Workday HCM
Xero
Zendesk Sell
Zoom
Databases
Files & Object Storage
SQL Data Query
SSH Tunnel Setup for Hosted Database Systems
SQL Playground Editor
SQL Transformations
DBT Cloud Transformations
Terraform: Reverse Terraforming
Sync Bridge (Data Pipelines)
Create a Sync Bridge
Manually Run a Sync Bridge
Deleting a Sync Bridge
Historical Re-sync
Analytics
Access Analytics
Snowflake Usage Analytics
Data Catalog
Create the Catalog
Populate the Catalog
Access the Catalog
Data Warehouse Clouds
❄️Snowflake
Open Source DW Models
Alerts & Notifications
Slack Notifications
Logs & Monitoring
Security
Callback Links
Service Level Agreement (SLA)
Release Notes
July 2023
June 2023
May 2023
April 2023
Q3 2022
Q4 2022
Community Overview
Contributor Agreements
Code Contribution Guide
About
Customer Support
License
Viewpoint
Credit Consumption Breakdown
Docs powered by
Archbee
website logo
Connectors
Databases

Teradata

3min

Teradata is one of the original enterprise database technologies that exist both on-premise and in the cloud. Teradata's robust platform is a best-in-class enterprise data platform, and its database technology is capable of handling massive transactional and analytical workloads.

Teradata Prerequisites:

  • 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
    • We suggest creating a new read-only user and new role to delineate this user service account for DLH.io from any other user access to your database, however, using an existing user and/or role is acceptable:
    • Create a Read-Only DLH.io user in your Teradata instance
      • We suggest creating a new user specific to DLH.io for read only access to your Teradata database(s), but you may already have an existing user in which case you can ignore this step:
        • Create a new user for DataLakeHouse.io using the following or similar example Teradata logic replacing <new_username> with a user name that you choose (we recommend 'datalakehouse_ro' to signify a read-only user), and choose a good password that complies with your security policies: CREATE USER <new_username> AS PASSWORD = "tmp!password", PERM=1000000;
        • Grant the User Access to the Source Database
          • 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>;

Instructions (Basic Connector Setup)

Remember DLH.io connects to your database instance with credentials supplied by you. We store your credentials securely with our bank-grade protocols.

  1. On DLH.io, Enter your Credentials and Other Information in the Fields
    • Click on the Add New Source for Teradata, and in the resulting new source page update the form with your connection information...
    • 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
  2. 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



Updated 22 Jul 2023
Did this page help you?
PREVIOUS
Handling a DDL Change for SQL Server CDC Enabled Tables
NEXT
Teradata Vantage Cloud
Docs powered by
Archbee
TABLE OF CONTENTS
Teradata Prerequisites:
Instructions (Basic Connector Setup)
Docs powered by
Archbee