Sitecore databases - an overview

Recently a colleague of mine wanted to know what all the databases around a Sitecore installation are for. While there is some scattered info here and there, and you can find for each database appropriate documentation in the Sitecore docs, there was nowhere a complete (or near complete) overview. This post aims on providing some overview, which might still not be complete with regards to in depth information, but at least helps in getting a better picture.
It represent an overview of Sitecore at version 9.2, so is subject to change in the future.
Notice any discrepancy or missing database? Do give me a nudge and I'll add it.


Core

Contains all Sitecore's own item definitions that build up the content editor, and base templates, system items etc. If you want to extend Sitecore core functionality, this is where you go. Access through Sitecore admin desktop / content tree if switched to this database in desktop.

Master

All your implementation specific content items for content editing while in content editor or experience editor.

Web

All your published content items. This is what is served on your published url's

Exm master

The EXM database stores the email dispatch queue used by the EXM Dispatch roles to handle email generation and dispatching.

Stores the email address of suppressed email recipients in the Suppressed table. Email addresses are removed when a contact executes the right to be forgotten.

ExperienceForms

Contains all data collected by Sitecore forms used on your site. Where the data is linked to specific field id's of the form's definitions.

MarketingAutomation

Marketing automation. Contains all your marketing automation instance info. Which contact is enrolled to which plan, is in which state etc. including the pool of activities to process.


Messaging

The Message bus is a message transport mechanism which allows application roles to communicate across boundaries. Based on Rebus.This database stores the messages that are to be transported

Processing.Pools

Contains references to contacts, interactions etc. that are queued for processing by one of the worker processes.

ProcessingEngineStorage

Stores data related to Sitecore Cortex, like projection results and trained learning models.

ProcessingEngineTasks

Stores tasks to be processed by Sitecore cortex processing engine.

Processing.Tasks

Stores processing tasks related to history aggregation and distributed processing.

ReferenceData

Reference Data is common data referenced by data used across the Sitecore Experience Platform, for example while collecting, processing, or reporting. Examples are marketing taxonomies such as Campaigns, Goals, and Outcomes, as well as IP Geolocation or device information.

Reporting

Contains aggregated results from xDB data that is used in dashboard/reports/diagrams in experience analytics.

Xdb.Collection.Shard0

Contacts and their interactions and device profiles are stored here.

Xdb.Collection.shardX

Contacts and there interactions and device profiles are stored here. You can have as many shards as you want/configure for scalability.

ShardMapManager

Shard manager keeps track of which parts of data are stored in which shard database, and informs your application layer to load which shard for which data.


Reacties

Een reactie posten

Populaire posts van deze blog

I Robot - Sitecore JSS visitor identification

While working on a Sitecore JSS solution that interacts with our Sitecore solution that hosts some api endpoints for us and add .net session state to cache some user bound data we noticed some unexpected behavior with respect to the session state on our test environments. Our session was configured to expire after 20 minutes of idleness, but no matter what our behavior was: idle or active our session seem to be reset much faster. After much debugging we couldn't find anything wrong with our own code, so we started considering options where maybe Sitecore could influence this. One of the suspects was Sitecore's robot detection mechanism that had given us trouble around session expiry in the past. We started by disabling robot detection. And this indeed seemed to resolve our session disappearing issue. So it was confirmed, we were identified as a robot. Further information proved that indeed, when classified as a robot visitor, Sitecore analytics settings set the session e...
Meer lezen

Get off my lawn - A journey from Sitecore MVC to the JSS world

A journey from MVC to JSS During Sitecore Symposium 2019 I gave a presentation about our journey as a company and developer community on moving from a Sitecore MVC mindset and specialization towards the Sitecore JSS world. This blog summarizes the most important take aways from this presentation. Working together One of the challenges we faced as a company was finding a good way of working together between front-end and Sitecore back-end developers. Coming from a distant past where we had front-end developers delivered static HTML, CSS and JS files and having a Sitecore developer transforming and migrating this into a Sitecore .NET solution, we evolved into an eco-system where front-end developers started working inside the .NET solution and worked with Razor files and more modern frameworks then JQuery such as AngularJS or React. This was fine for a while, but with Angular coming with newer versions and a need from UX perspective to deliver single page application experiences...
Meer lezen

Sitecore JSS - Sitecore first

JSS - Sitecore First! Recently I started a project where we are upgrading an existing Sitecore 9 MVC portal with AngularJS to Sitecore JSS with Angular 7. With this portal being already implemented, and content preexisting in the solution we wanted to start this with a Sitecore first approach. In this approach we create the JSS layout service endpoint that return Json containing the same content a component now renders in the MVC controller rendering, reusing existing content, templates etc. First things first To start, obviously as a Sitecore developer you have to install the Sitecore JSS server components into your environment. After that you create a Sitedefinition like entry for your JavaScriptServices where you register your JSS app and set the start item for your app root. You setup your API key as defined in the JSS doc site . To make sure your Sitecore instance is aware of this app and where in the Sitecore tree it 'lives'. You extend your Sitecore SiteDefin...
Meer lezen