A schema is the owner of a database object. As we are just beginning, all the objects in the database will have only one owner; however, if you use third party applications you might see additional schema owners. A good practice example can be found in the AdventureWorks database provided by Microsoft. Schemas are helpful when we want to apply security to a database. We will touch more on this in the lesson on Security.

Microsoft Access does not have a concept of schemas.

A schema identifies the owner of an object and virtually all objects can have an owner. Most of the databases you will use will only have one schema; however, in some larger databases multiple schemas are often used.

Think of a schema as a way to group some of your objects together. This then allows you to give permissions to users or roles into that grouping rather than the individual objects.