SQL Server data and log file placement for Lync Server 2013


Topic Last Modified: 2013-02-21

During the planning and deployment of Microsoft SQL Server 2012 or Microsoft SQL Server 2008 R2 SP1 for your Lync Server 2013 Front End pool, an important consideration is the placement of data and log files onto physical hard disks for performance. The recommended disk configuration is to implement a 1+0 RAID set using 6 spindles. Placing all database and log files that are used by the Front End pool and associated server roles and services (that is, Archiving and Monitoring Server, Lync Server Response Group service, Lync Server Call Park service) onto the RAID drive set using the Lync Server Deployment Wizard will result in a configuration that has been tested for good performance. The database files and what they are responsible for is detailed in the following table.


If your policies and SQL Server configurations require a more specialized installation, the database and log files can be installed to any pre-defined location using the Lync Server Management Shell. See Database installation using Lync Server Management Shell in Lync Server 2013 for more details.

Data and Log Files for Central Management Store

Central Management store database files Data file or log purpose


Transaction log file for the Central Management store


Maintains the configuration of the current Lync Server 2013 topology, as defined and published by Topology Builder


Location Information service data file


Transaction log for the Location Information service data file

Data and Log files for User, Conferencing, and Address Book

Core Lync Server 2013 database files Data file or log purpose


Persistent user data (for example, access control lists (ACLs), contacts, scheduled conferences)


Transaction log for Rtc data


Maintains transient user data (presence runtime data)


Transaction log for Rtcdyn data


Real-time communications (RTC) address book database is the SQL Server repository where Address Book service information is stored


Transaction log for Address Book Service


Hosts the conference directory


Maintains the backup for user data


Transaction log for Rtcxds data

Data and Log Files for Call Park and Response Group

Application database Data file or log purpose


Dynamic information database for the Call Park application


Transaction log for Call Park application data file


Lync Server Response Group service data file for the configuration of the services


Transaction log file for the Response Group application configuration


Response Group service data file for runtime operations


Transaction log for the Response Group service runtime data file

Data and Log Files for Archiving and Monitoring Server

Archiving and Monitoring database files Data file or log purpose


Data store for the call detail recording (CDR) process of the Monitoring Server


Transaction log for call detail recording (CDR) data


Quality of Experience data file stored from the Monitoring Server


Transaction log for Monitoring data


Data file for the retention of instant messaging and conferencing data on an Archiving Server


Transaction log for Archiving data

In this topic, references are made to disk and to RAID set. Note that in the configuration of SQL Server resources, referring to a disk means a single hardware device. A hard disk drive with two partitions, one holding log files and the other partition holding data files, is not the same as two disks, each dedicated to either log or data files.

In reference to RAID sets, there are a number of different RAID technologies from various vendors. And, with the proliferation of storage area networks (SAN), RAID sets dedicated to a single system are rarer. You should consult with your RAID or SAN vendor to determine what the best configuration is for your disk layout when configuring for SQL Server performance with Lync Server 2013.

Note also that not all disk drives are created equally; some perform better than others. Even drives from the same manufacturer can vary in performance because of rotational speed, hardware cache size, and other factors.