Standard Databases

Standard Databases

Master Database

  • A standard database that contains every version of every item, including unpublished versions
  • Contains both the history of the Web site and the work in progress
  • Main repository of all Sitecore items
  • Stores data for the Content Management Server
  • Contains all versions of content, all languages, published and unpublished in any workflow state
  • Also known as the work-in-progress database
  • Many of the Sitecore Client User Interfaces directly access content stored in this database:
    • Page Editor
    • Content Editor
    • Preview
    • Media Library
    • Desktop

Web Database

  • A standard database that contains items available on the published Web site
  • Contains the latest publishable version of every item that has been published in every language that has been published
  • Stores data for the Content Delivery Server
  • Supports the production web site
  • Contains only the most recent published version of content
  • Contains the latest version of published content that has completed workflow
  • Also known as the Live database
  • The Sitecore Debug tool directly accesses content stored in this database:

Core Database

  • A standard database that contains configuration information for the Sitecore user interfaces
  • Contains ASP.NET membership schema
  • Contains Recycle Bin for storing deleted items
  • Contains Archive for storing archived items
  • Contains HTML Editor Profiles that control the display of toolbars in Rich Text Editor fields

Content Database

  • References the Sitecore database that the CMS user interface components interact with
  • Not a distinct physical database like Master, Web, or Core
  • The default is the Master database but the Sitecore Desktop can be used to change it to another database

Context Database

  • References the Sitecore database associated with the current HTTP request
  • Not a distinct physical database like Master, Web, or Core
  • Presentation components that retrieve content for display almost always access the context database rather than referencing a database by name

Sources