Page database structure

CMS_Tree

Stores:

• Data that determines the position of pages in the website content tree
• Basic page properties that are shared between all language versions of the same page

Contains only one record for each page, regardless of the number of language versions. The table doesn’t store any versioned data.

CMS_Document

Stores:

• Page properties that have unique values for each language version
• The content of editable regions
• The data of editor widgets

May contain multiple records per page, one for each language version. Some of the page columns are versioned.

Coupled data tables
(CONTENT_<doc type>)

Stores the fields of individual page types.

For example, the News page type has the CONTENT_News coupled table with the columns defined for news pages, such as NewsTitle, NewsSummary, NewsText.

• Records in the coupled data tables are bound to pages through the DocumentForeignKeyValue column of the CMS_Document table.
• The page type of tree nodes is determined by the NodeClassID column in the CMS_Tree table.
• Container page types, such as Folder, do not have a coupled table.
• Every language version of a page has its own record in the corresponding coupled data table.
• All columns in coupled data tables are versioned.

CMS_Attachment

Stores files uploaded to the database as page attachments.

Includes all types of page attachments:

• Unsorted attachments added on the Properties -> Attachments tab in the Pages application. Such attachments are linked to the related page by storing its identifier (AttachmentDocumentID column).

• Attachments uploaded through specific page fields (of either the File or Attachments data type) on the Form or Content tab in the Pages application. Such fields are represented by columns in the given page type’s coupled data table.

  • Page type fields of the File data type store a GUID value, which identifies the corresponding attachment in the CMS_Attachment table.
  • For fields of the Attachments data type, the value in the database is always empty. Instead, the given records in the CMS_Attachment table store an identifier of the related page (AttachmentDocumentID column) and a GUID value that identifies the specific field in the page type’s form definition (AttachmentGroupGUID column).

CMS_VersionHistory

Stores page versions, including older versions and versions that are being edited. When a version is published, the system updates the corresponding records in the CMS_Tree and CMS_Document tables using the data of the version record.

CMS_AttachmentHistory

Stores attachments of page versions. The main purpose of this table is to avoid redundancy for page versions that use the same attachments.

When a page version is published, the system updates the records in the CMS_Attachment table using the data of the version record.

CMS_VersionAttachment

Stores relationships between page versions and their page attachments.

CMS_Relationship

Stores records representing relationships between two pages. Used for both:

• Standard named relationships
• Ad-hoc relationships that represent re-use of a page’s content within a Pages field of another page (see Advanced content modeling)

CMS_RelationshipName

Stores the relationship names (types) defined in the system.

CMS_RelationshipNameSite

Binding table that connects relationship names to websites. Each entry indicates that a relationship can be used on a given site.