A database schema is a blueprint or structure of a database that describes how data is organized and structured. It defines the organization of data as a blueprint of how the database is constructed and the relationships between tables in a given database. A schema can contain formulas representing integrity constraints specifically for an application and the constraints specifically for a type of database, all expressed in the same database language. In a relational database, the schema defines the tables, fields, relationships, views, indexes, packages, procedures, functions, queues, triggers, types, sequences, materialized views, synonyms, database links, directories, XML schemas, and other elements. A database schema is considered the “blueprint” of a database which describes how the data may relate to other tables or other data models. It is a collection of logical structures of data, or schema objects, owned by a database user and has the same name as that user. Each user owns a single schema, and schema objects can be created and manipulated with SQL. The primary purpose of creating a database schema is to ensure the integrity of the data stored in the database, so it can confidently be used by the broader business for applications such as business intelligence. Having the right schema is an essential element of data modeling, especially for organizations that rely on data to drive multiple parts of their business.