From the course: Exploring Performance and Scale with Data Options in Azure

Unlock the full course today

Join today to access over 22,700 courses taught by industry experts or purchase this course individually.

Designing for relational

Designing for relational - Azure Tutorial

From the course: Exploring Performance and Scale with Data Options in Azure

Start my 1-month free trial

Designing for relational

“

- [Instructor] Designing for relational means that we're looking at the database engine as something that has a standard, relational model. What that means, it has tables and entities that are related to each other. Tables have rows. There's primary keys and indexes that we can add to those tables to allow us to quickly get to the data that we want. We add indexes based on our access patterns that we use to go after the data. So if we include a column, we might add an index on that column, which then makes it easier and faster to get to that specific rows. We also use concepts like normalization, which let us apply rules to make sure that our data follows efficiency constructs like not having duplicate data, having a primary key that uniquely identifies a row. We also talked about relational integrity, and how a given table, like in order detail, requires that the order header record exists before you can add the detail…

Contents