Cheat sheet with the key network elements you need to connect with your Teradata VaaS on Azure and a detailed explanation.
Category: Relational Databases
A Relational Database consists of a set of logically related tables.
A table is a two-dimensional representation of data consisting of rows and
columns.
A row is one instance of all the columns of a table. E.g., the information about a single employee is in one row, such as full name, ID number, address, etc.
The sequence of the rows in a table is arbitrary.
We design Relational Databases to protect access to data and retain its value and integrity.
The key idea about Relational Databases is that they permit associations by data value across more than one table.
Relational Databases do not use access paths to locate data. Instead, data connections are made through data values. In other words, the database software makes data connections by matching values in one column with the values in a corresponding column in another table. We call this connection JOIN.
As we have already said, a Relational Database is a collection of relational tables. The database collections are stored in a single installation of a Relational Database Management System (RDBMS). The words “management system” indicate that not only is this a relational database, but also there is underlying software to provide additional functions. These features include transaction integrity, security, relational operations (table scans, index scans, projections, selections, joins, aggregations), etc.
Many vendors in the market build RDBMS. While all of them allow establishing relationships among the data in different tables, there are critical differences in their internal architecture. Depending on your use case and requirements, you may choose one RDBMS or another.
In this category, you will find posts that refer to use cases, best practices and know-how instructions on Relational Databases from different vendors.
Teradata VaaS on GCP: Network configuration
A cheat sheet with the indispensable network elements you need to connect with your Teradata VaaS on GCP and a detailed explanation.
From Zero to Hero in Cross-Site Restores in Teradata
The Cross-Site Restores feature in VantageCloud Enterprise allows you to quickly create a Disaster Recovery site for your Production database.
Teradata’s Cloud-Native Database
Teradata has just launched a Cloud-native database, VantageCloud Lake. In this post, I discuss its high-level architecture.
Azure Synapse Analytics: an Unusual Introduction
This post is a 101 introduction to Azure Synapse including information that it is not easily found in the online documentation and courses.
Customer Churn Demo
This post explains how to predict customer churn, a typical Machine Learning use case, using Google Cloud services.