11 Tricks to teach you how to play database design

How do we pick out the data we want when we meet a huge amount of data in our daily work? Is it a blind search, or is it a search for a new solution or a trick to get it? When designing a data form, developers tend to follow three commonly used forms, which they consider to be the only way to design. However, since the developer had this mindset at the outset, the design of the data form became entrenched and hindered its innovation.

The author Shivprasad from the usual work project accumulated some experience, introduced us to 11 of the production of data form skills, when the design to the data form production, may wish to refer to this to enrich our application experience.

Rule 1: What is the nature of the application (OLTP or OLAP)?

When you start making data form design, first of all, what is the nature of the program you designed? Transactional or analytical? You will find that many developers apply the general rules by default, and then consider performance issues without considering the nature of the application.

For transactional and analytical, let's look at the difference.

Transactional: This application, users are more interested in crud, that is, create, read, update and delete records. This data, the official name of the bit OLTP.

Analytical: Users are interested in analysis, reporting, forecasting, etc. Such databases are rarely embedded and updated. The main purpose is to obtain and analyze data as soon as possible. The official name is called OLAP.

In other words, if you want to focus on embedding, updating, and deleting, you can choose a regular form design or create a simple, highly regulated data architecture.

Here is a simple chart with the name and address displayed on the left, a simple regular form designed with a non-standard structure.

Rule 2: Divide the data into different chunks by logical thinking, making life simpler

This rule is actually the first paradigm in the "three paradigms". The goal of this design is to provide you with this functionality when you need to query multiple string parsing functions, such as substring, charindexetc.

For example, watch the chart below, and if you want to query a student's name, make a distinction by "Koirala" and "Harisingh".

Therefore, a better way is to break the logic of data so that we can write simpler, easier to query forms.

(Responsible editor: The good of the Legacy)