This post explains how to differentiate among the different types of NoSQL databases. and how to plan a migration from PostgreSQL to MongoDB.
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.
Planning a Database Migration
The secret sauce of a successful migration is planning and architecture. In this post we discuss the different aspects you must consider.
Cookbook to transform a Teradata VMware Virtual Machine into a Hyper-V one
How to make a Teradata database running on a VMware virtual machine run on a Hyper-V virtual machine instead.
Cookbook to set up a Teradata Virtual Machine in Azure
Quick Start Guide to set up a Teradata Virtual Machine in Azure.