Office Communications Server 2007 R2 Enterprise Edition stores data in SQL Server 2008 and SQL Server 2005 with SP2 databases, as well as in specific file shares.

Note:
User information, including Communicator Web Access user-specific information (such as contact lists) is stored either in Active Directory Domain Services or in the Office Communications Server 2007 R2 database. This means that the failure of an individual computer (or set of computers) does not affect user information in any way, as long as Active Directory Domain Services and the Office Communications Server 2007 R2 database are maintained.

The following table describes the databases used by Office Communications Server 2007 R2 Enterprise Edition, except Active Directory Domain Services databases, and where they are located.

Table 1. Enterprise Edition Databases

Type of data Database Database location

Persistent user data (such as ACLs, contacts, home server or pool data, and scheduled conferences); includes user contact lists, as well as allow and block lists

RTC

SQL Server 2005 with SP2 or SQL Server 2008 database on the back-end server.

Persistent Office Communications Server 2007 R2 global-level, pool-level, and computer-level settings

RTCConfig

SQL Server 2008 or SQL Server 2005 with SP2 database on the back-end server.

Transient user data (such as endpoints and subscriptions, active conferencing servers, and transient conferencing states)

RTCDyn

SQL Server 2008 or SQL Server 2005 with SP2 database on the back-end server.

Address Book

RTCab

SQL Server 2008 or SQL Server 2005 with SP2 database on the back-end server.

Archiving data

LCSLog (default name)

SQL Server 2008 or SQL Server 2005 with SP2 database for archiving data, typically deployed on a separate computer, the Archiving Server.

Call Detail Record (CDR) data

LcsCDR

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the back-end database and always deployed on the same server, in the same instance, as the QoE database.

Quality of Experience (QoE) data

QoEMetrics

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the back-end database and always deployed on the same server, in the same instance, as the CDR database.

Group Chat data

User-specified database name

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the Group Chat Server.

Group Chat compliance data

User-specified database name

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the Group Chat Compliance service, and can be the same database instance that is used for Group Chat data. The Channel service writes each message to Message Queuing on the Compliance Server, and the Compliance service then writes the message to the database temporarily before it processes the message. The Compliance service processes messages in the database and writes them to XML files.

Transient Response Group Service data (such as agent sign-in state and call waiting data)

ACDDyn

SQL Server 2008 or SQL Server 2005 with SP2 database on the back-end server.

The following table describes the file shares used by Office Communications Server 2007 R2 Enterprise Edition and where they are located.

Table 2. Enterprise Edition File Shares

Type of data File share File share location

Address book download files

User-specified (UNC path)

Typically created on a separate computer from the Enterprise Edition Front End Server (recommended), such as a file server, in a user-created shared NTFS folder. This file share is often on the same computer as meeting content.

Meeting content (such as Microsoft Office PowerPoint presentations, Q&A logs, polling data, chat data, and uploaded content)

User-specified (UNC path)

Typically created on a separate computer from the Enterprise Edition Front End Server (recommended), such as a file server, in a user-created shared NTFS folder. This file share is often on the same computer as the address book files.

Meeting content metadata (XML data that describes the meeting content, such as the date and time that a presentation is uploaded)

User-specified (UNC path)

Typically created on a separate computer from the Enterprise Edition Front End Server (recommended), such as a file server, in a user-created shared NTFS folder. This file share is often on the same computer as the address book files.

Meeting content compliance log (XML data that records content upload activities, along with the uploaded meeting content)

User-specified (UNC path)

Typically created on a separate computer from the Enterprise Edition Front End Server (recommended), such as a file server, in a user-created shared NTFS folder. This file share is often on the same computer as the address book files.

Application data files (used internally by the application server component)

User-specified (UNC path)

Typically created on a separate computer from the Enterprise Edition Front End Server (recommended), such as a file server, in a user-created shared NTFS folder.

Group Chat Web and compliance folders (to store files uploaded to the Group Chat Web service)

User-specified UNC path

A file share that can be accessed by all of the Group Chat Servers and services in the pool.

Group Chat compliance XML files

User-specified UNC path

The file share used to store Group Chat compliance data.

Update files (for Device Update Service)

User-specified UNC path

Typically created on a separate computer from the Enterprise Edition Front End Server (recommended), such as a file server, in a user-created shared NTFS folder.