Is this really the version you are looking for? Kentico Xperience 11 Documentation is no longer updated. Use the switcher in the header to choose your product version.
Kentico EMS required
Features described on this page require the Kentico EMS license.
When using contact management on high‑traffic websites, the system needs to store a very large volume of data in order to keep records of all contacts, their activities and other related information. This may complicate database administration and make it difficult to perform regular backups. For these reasons, Kentico provides a way to move all tables and database objects associated with contact management to a separate database (including the currently stored data). Doing so allows easier management of the application's main database, without the need to deal with the contact data.
There can only be one separated contact management database for the entire system, even when hosting multiple websites. It is not possible to create a different database for each site.
The separation procedure affects the following database tables:
Use the following steps to separate the system's contact management data into a different database.
Warning
Database separation on Amazon RDS
Separating the contact management database on Amazon RDS is not supported.
Database separation on Microsoft Azure
If your SQL database is hosted on Microsoft Azure, you need to manually perform some parts of the procedure:
Open the System application.
Select the DB separation tab and click Separate contact management database.
Specify the SQL server to which you wish to transfer the contact management database and enter the connection credentials.
You can identify the server through its name or IP address.
It is possible to use a different server than the one containing the main database.
The separated database may be hosted on all server types supported by Kentico.
Continue by clicking Next.
In Step 2, choose to either:
Create a new database for the contact management DB objects and data
Import the DB objects and data into an existing database on the server specified in the previous step.
Type the name of the target database into the appropriate field.
Click Disable tasks.
You need to prevent all scheduled tasks in the system from running, because the database will be unavailable during the separation process. If a task is currently being executed when you click the button, the disabling action waits until the task is finished. The tasks will automatically be enabled again when the separation is completed.
Click Next to begin the separation.
When the process is completed, all contact management data is transferred to the new database. If you view your application's web.config file, you can notice that an additional connection string for the new contact management database is now present in the <connectionStrings> section:
<add name="CMSOMConnectionString" connectionString="..." />Click Finish in the final step of the wizard.
Database separation on web farms
If your application is running on multiple servers in a Web farm environment, you need to manually copy the CMSOMConnectionstring key into the web.config files of all other servers, otherwise they will not be functional.
The new database status is reflected on the General tab of the System application, in the Database information section.
All functionality of the website and administration interface remains the same as before the separation.
If you wish to reverse the process and return everything back to a single database, follow the instructions in Rejoining the contact management database.
Querying data from separated databases on Azure SQL
If you are using a Microsoft Azure SQL database (opens in a new tab) and wish to run custom queries that load data from a separated database, you need to utilize elastic queries (opens in a new tab) (cross-database querying):
For detailed information, see the Query across cloud databases (opens in a new tab) article.