Episerver uses Microsoft SQL Server to store content and other information created in the system. Episerver supports all database editions including SQL Azure. See the system requirements for specific versions of SQL Server that Episerver supports.
A database schema is a way to logically group objects such as tables, views and stored procedures, in the database. When you create a new site from the Visual Studio integration, it automatically creates the database with the Episerver schema. Each version of the database schema targets a specific version of the product. The following topics show how to deploy a database from development to production.
If you need to install database schema on an empty database, you can use Initialize-EPiDatabase cmdlet from the Package Manager in Visual Studio. The Initialize-EPiDatabase cmdlet installs the database schemas included in the installed NuGet packages.
You can also configure a site to automatically create the database schema during site initialization. When the site starts up, Episerver checks if the schema is installed in the current database as specified by the connection string. If no schema is found and automatic creation is enabled, it executes an SQL script that adds the schema to the database.
To enable automatic schema creation, add attribute createDatabaseSchema="true" to the episerver.framework element in configuration as shown below:
The automatic schema creation is done using the same process as schema updates and it therefore allows you to interact with the schema creation process by registering an implementation of IDatabaseSchemaValidator in the Episerver IOC container. See Automatic schema updates for further information and examples. Automatic database schema creation will be available for EPiServer.Commerce in upcoming versions.
If you want to manually deploy the schema, you find the SQL script files in the EPiServer.CMS.Core NuGet package under the tools subfolder.
If the web application was configured to use Windows Workflow Foundation or SQL Membership provider module, you need to deploy the Windows Workflow Foundation and the SQL Membership provider database schema manually. The Initialize-EPiDatabase cmdlet does not install these.
Consider the following recommendations:
Last updated: Oct 26, 2016