DBO stands for “database owner,” and it’s the default schema you’ll encounter in SQL Server databases. If you’ve seen “dbo” prefixed to table names in a query (like dbo.Customers or dbo.Orders), it’s telling SQL Server where to find that object. While DBO has a few niche meanings in chemistry and medicine, the database context is overwhelmingly the most common reason people search for this term.
DBO as a Database Schema
In SQL Server, every database object (tables, views, stored procedures) lives inside a container called a schema. Think of a schema like a folder on your computer: it organizes objects and controls who can access them. The dbo schema is the default schema that exists in every SQL Server database, and it’s owned by the dbo user account.
When you create a new table or other object without specifying a schema, SQL Server places it in dbo by default. Similarly, when you query an object using just its name (a “one-part name” like SELECT * FROM Customers), SQL Server first checks your personal default schema. If it doesn’t find the object there, it automatically checks the dbo schema next. This fallback behavior is why dbo ends up holding the majority of objects in most databases.
New users created in SQL Server are assigned dbo as their default schema. That said, being assigned to the dbo schema doesn’t give a user the same permissions as the dbo user account. Permissions in SQL Server flow to the objects inside a schema, not to the people associated with it. The dbo schema is also one of four built-in schemas that cannot be deleted from any database.
Why You See “dbo.” in Queries
When someone writes dbo.Employees in a SQL query, the “dbo” part is called a schema qualifier. It explicitly tells the database engine which schema to look in, removing any ambiguity. This matters in larger databases where multiple schemas might contain objects with similar names. A table called dbo.Users and hr.Users could coexist in the same database, and the schema prefix keeps them distinct.
Using the dbo prefix is considered good practice even when it’s technically optional. It makes queries slightly faster because SQL Server doesn’t have to search through other schemas first, and it makes your code clearer to anyone reading it later. In most small to mid-size databases, virtually every table sits in the dbo schema, so you’ll see this prefix constantly.
DBO User vs. DBO Schema
This distinction trips up a lot of people. The dbo user account is a special built-in account that maps to the database owner, the person (or login) who created or owns the database. This account has full permissions to do anything inside that database. The dbo schema is simply the default organizational container that this account owns.
A regular user who happens to have dbo set as their default schema does not inherit the elevated permissions of the dbo user account. They still need explicit permissions granted to them. The naming overlap between the user and the schema is a source of confusion, but they serve different purposes: one controls access, the other organizes objects.
Other Meanings of DBO
Outside of databases, DBO occasionally appears in specialized fields, though none of these meanings are nearly as common in everyday searches.
- Diazabicyclooctane (DBO) scaffold: A molecular structure used in pharmaceutical research to design antibiotics. Avibactam, a clinically available drug that fights antibiotic-resistant bacteria, is built on the DBO scaffold. These compounds work by blocking enzymes that bacteria use to break down antibiotics.
- Dibutyltin oxide: An industrial chemical in the organotin family, used as a stabilizer and in antifouling coatings. It’s toxic at elevated exposures, and workplace safety limits cap airborne concentration at 0.1 mg per cubic meter over an eight-hour shift.
- Distal biliary obstruction: A medical condition where the lower portion of the bile duct becomes blocked, often by a tumor. It typically presents as painless jaundice, pale stools, dark urine, and weight loss.
If you encountered “dbo” in a SQL query, a database tool, or a programming tutorial, the database owner schema is almost certainly what it refers to. It’s one of the first things you’ll run into when working with SQL Server, and understanding it as a default container for database objects covers most of what you need to know.