Relational Database

Relational database management system

The relational database management system is the backbone of every database. No matter what relational database you work with, you’ll be using its RDBMS to interact with its data.

0
24

How to choose a good primary key

In an SQL database, the primary key is an essential part of any table. Choosing the right primary key for each table requires us to take different factors into consideration if we want to guarantee simplicity, adaptability, and performance.

0
17

DB-related jobs and the differences between them

In small companies, there is usually only one database job. The person in that position may be an architect one day, a designer the next day, a programmer another day, an administrator the day after that, and sometimes even an analyst or even a data scientist.

0
18

What are the differences between OLTP and OLAP?

Confused by online transaction processing (OLTP) and online analytical processing (OLAP) in the world of databases? Fear not. We have a simple explanation right here.

0
144

Always define a primary key for each table

In a relational database, each table should have a primary key (PK). A primary key has multiple advantages for a table, including a:

0
20

What does cardinality mean in a database?

Cardinality in an SQL database isn’t just a number representing rows in a table. It also has an impact on query performance. Learn how database cardinality works in this article.

0
20

Types of indexes in a relational database

Using database indexes is one of the easiest ways to improve the overall performance of a database, more specifically query performance, if you select the right type. Knowing the types of indexes in SQL is very important since different indexes provide different benefits

0
17

Primary keys vs. unique keys: differences

In relational database tables, we use ‘keys’ to identify and find information more easily, or to show the relationships between the data of two different tables. Two of these identifiers are primary keys, and unique keys. Let’s take a closer look.

0
20

SQL performance best practices

By far the easiest (and biggest) performance improvement comes from good use of indexes. I’ll break this down into two categories: (1), knowing what’s possible, and (2) knowing what you’re actually getting.

0
11

7 reasons why developers should learn SQL

In fact, SQL is an important tool that can help with everything from performance optimization to debugging. Let’s take a look at just a few of the reasons why developers should learn SQL:

0
13

3 common foreign key mistakes

Ultimately, most common foreign key mistakes are the result of sloppy planning. Taking a little extra time to plan out your database schema up front can help you avoid headaches later down the line.

0
13

Quick guide to physical data modeling

The diagrams or documents created act as blueprints for the final result and keeps the project on track, enhances visibility to all stakeholders, ensures consistency, and helps the developer avoid errors that might be difficult or costly to correct at later stages.

0
17

Logical vs physical data dictionary

Data Dictionary is a description of data structures (read about two basic types) and you can distinguish logical and physical Data Dictionaries.

0
13

Reasons why databases don’t get documented

Here is my subjective list of reasons why databases don’t get documented. In a later article on why it is bad for your team, project and organization.

0
15

Document functions & stored procedure in DB

Doing research for this article, I found out that despite of those techniques having been here for many years and a lot of people asking questions, there aren’t many useful resources with a compilation of best practices.

0
38

Lack of comments makes DB documentation useless

This documentation included many data details like data type, precision, format, etc. but to my surprise it did not include the most important one – a description of a meaning of each column

0
15

Who do you document databases for

If anyone would need something, they can always talk to you, since you know all the answers. In this article, I’d like to show many people require to understand the design and would be very grateful for a useful documentation.

0
14

Document cross-database table relationships

Data in today’s information systems are organized into databases. A database is a logical subset of data tables and scripts hosted on a server. This division is often artificial and there are no strict logical boundaries between data assets.

0
35

Sort by: