Configuring session database servers

Last updated Thursday, July 12, 2018 in Sitecore Experience Platform for Developer, Administrator

In the xDB, you configure a session state database to track all contact interactions and to maintain visitor session state. Configuring out of process session state is particularly important if you have deployed an environment with multiple content delivery servers.

You can configure a session state database on the same server as other roles, such as content delivery, but for better performance and scalability, create a separate session database server.

Depending on which database system you want to use when you configure your session state database, you need to use a session state provider. Sitecore comes with the following providers:

  • Sitecore ASP.NET Session State Provider for Redis
  • Sitecore ASP.NET Session State Provider for MongoDB
  • Sitecore ASP.NET Session State Provider for Microsoft SQL Server


A dedicated Sitecore instance is not required when configuring a dedicated session state database server.

You can choose to use the same database for both session states but to ensure that the system can distinguish between the private and shared session entries, you must remember to configure the correct attribute in the web.config and the Sitecore.Analytics.Tracking.config files.

Follow these instructions to configure session state providers:

Send feedback about the documentation to