Skip to main content

DCL (Data Control Language)

Imagine you have a safe with very valuable toys. You decide who can open the safe, who can see what's inside, and who cannot touch anything.

DCL (Data Control Language) is like the magic key or the permissions you use to say:

  • "You can see my toys."
  • "You can play, but not take them out of the box."
  • "You cannot even look."

Just like in a video game there are roles (like “player”, “admin”, “spectator”), in databases you decide what each person can do with the data.

What is DCL? (technical definition)​

DCL stands for Data Control Language and is a part of the SQL language, which is used in databases.

SQL (Structured Query Language) is the language we use to talk to a database, to do things like:

  • View data (query).
  • Add data (insert).
  • Change data (update).
  • Delete data (delete).

But besides that, SQL also allows controlling who has permission to do those things, and that's where DCL comes in.

DCL is used to grant or revoke permissions to users over the data.

There are two main commands:

  • GRANT: gives permissions.
  • REVOKE: takes permissions away.

What is DCL used for?​

DCL (Data Control Language) is used to manage security and access to data in a database. In other words, it allows you to decide who can view, modify, or delete information, and who cannot.

Imagine you have a database with very important information, like:

  • Customers.
  • Money.
  • Passwords.

You cannot allow just anyone to do whatever they want, like accidentally deleting things or seeing private data.

That is why, with DCL you can:

  • Grant permissions to people who need to work with that data.
  • Revoke permissions from those who should not access or modify anything.

DCL protects data. It helps ensure that:

  • Only the boss sees the reports.
  • Only the cashier can change prices.
  • A guest only sees things, but doesn't touch them.

It's like putting locks and keys on a database.

Why is it important?​

  1. Data security: Prevents unauthorized people from accessing confidential information (like customer data, salaries, or passwords).

  2. Action control: You can allow certain users to only view data, but not modify or delete it.

  3. Error prevention: If you limit what a user can do, you also reduce the risk of accidental errors, like carelessly deleting a table.

  4. Accountability and auditing: You can know who has access to what and hold users accountable for the actions they perform.

Common uses of DCL (Real examples)​

  1. Granting permission to an employee to view data, but not modify it:
  • For example, Ana works in customer service. She needs to see the customer list, but she shouldn't be able to edit it.
  1. Preventing external users from accidentally deleting data:
  • Imagine an intern joins the company. You can give them only read permissions, so they don't delete anything by mistake.
  1. Revoking permissions from someone who no longer works at the company:
  • If Pedro resigns, all his permissions are revoked. He can no longer enter to see or change anything.

Practical Example​

In a company, there is a database with a table called customers. The boss wants Ana to be able to view customer information (make queries), but does not want her to be able to modify or delete it.

GRANT SELECT ON customers TO ana;
  • GRANT: Command to grant a permission
  • SELECT: Permission to view/read data from the table
  • ON customers: Applies to the table named customers
  • TO ana: Permission is granted to the user

If later on the boss decides to revoke that permission from Ana:

REVOKE SELECT ON customers FROM ana;
  • REVOKE: Command to revoke a permission.
  • SELECT: The read permission that will be revoked.
  • ON customers: From the customers table
  • FROM ana: This permission is revoked from the user ana.