Skip to content
datastudyguides

DP-900 · 2 Identify considerations for relational data on Azure

Database objects

Exam objective: Identify common database objects

Beyond tables, a relational database can hold views that present a query as a virtual table, stored procedures that package reusable logic, and indexes that speed up lookups.

A relational database holds more than tables. Three objects come up often: views, stored procedures and indexes.

A view is a virtual table defined by a SELECT query. Once created, you query it the same way as a table, which is handy for hiding a join behind a simple name.

CREATE VIEW Deliveries AS
SELECT OrderNo, City FROM Order
JOIN Customer ON Order.CustomerID = Customer.ID;

A stored procedure packages one or more SQL statements so an application can run them on command, usually passing in parameters such as an ID to act on.

An index is a sorted copy of one column with a pointer back to each matching row, similar to the index at the back of a book. It lets the database jump to matching rows instead of scanning the whole table. That speed has a cost: every insert, update or delete on an indexed column also has to update the index, so extra indexes can slow writes down.

On the exam, connect "virtual table from a query" to view, "reusable packaged logic" to stored procedure, and "speeds up lookups" to index.

Key points

  • A view is a virtual table based on a SELECT query, and you can query it the same way as a table.
  • A stored procedure holds SQL statements that run on command, often with parameters to make them reusable.
  • An index stores a sorted copy of one column with pointers back to the matching rows, so the database can find rows without scanning the whole table.
  • Indexes speed up reads but add overhead, because every insert, update or delete has to keep the index current too.

Exam trap

An index is not free. It speeds up the exact queries it supports, but every write to the indexed column also has to update the index, so adding indexes you do not need can slow writes down.

Check yourself

For each statement about indexes, select Yes if it is true. Otherwise, select No.

  • An index helps the database find matching rows faster.
  • Creating more indexes on a table never has any downside.
  • An index changes the data stored in the original table.

Go deeper on Microsoft Learn

Checked against Microsoft Learn on October 1, 2026.

How well do you know this?