Lync Database Requirements

The first SQL database required for a new Lync installation is the Central Management Store (CMS), which is used to store the configuration data that is replicated to all the Lync servers in the environment. Beyond the CMS, the Front End Servers also require databases for persistent and dynamic user data, and address book information. Additional databases are also used depending on specific optional features that might be deployed, such as the Response Group and Call Park services. Collectively, these databases are referred to as the Lync Back End databases, and the two database platforms that can be used for these are SQL 2008 R2 and SQL 2012.

Depending on the topology, it is also possible to collocate databases that are used by other Lync server roles with Lync Back End databases. For example, the Archiving and Monitoring Server roles both have their own databases, and both can be installed on the same SQL instance as the Lync Back End databases. The Persistent Chat databases can also be installed on the same SQL system with the Lync Back End databases. The decision as to whether to collocate these databases on the same SQL system with each other or with the Lync Back End databases is largely a matter of whether performance requirements can be met. With that in mind, these configuration decisions need to be considered on a case-by-case basis. All the database collocation possibilities mentioned previously are applicable to Enterprise Edition pools only. This is because the Standard Edition uses SQL Express, which does not meet the database requirements for any of the other Lync server roles.