Deploying OCS R2 – SQL
Update Sat December 27 - My colleague Thomas Binder in Austria noted some discrepancies in the documentation around the terms database and instance, so I wanted to note where I found the information to say that unique instances was the supported configuration. In the Office Communications Server 2007 R2 Documentation.chm file the section on Back-End Database Topology has this text -
Hosting Multiple SQL Server Applications
A server that runs an Office Communications Server database (Back-End Database, Archiving database, or Monitoring database) can host other SQL Server applications if those applications are hosted in different SQL Server instances. The SQL Server instance that hosts any Office Communications Server database must be dedicated.
I am continuing the building of my virtual images in preparation for the RTM of R2 and today that meant building my SQL server. I chose SQL 2005 as this version is supported for both OCS 2007 and OCS 2007 R2 allowing me the most flexibility as well I have not begun to look into SQL 2008 given that I use it only for the application I do know.
I am installing SQL 2005 with 3 instances for R2 –
- poolbe - backend for the R2 pool
- archiving – Archiving of IM headers and/or body
- monitoring – CDR and Monitoring. There are separate databases for CDR and QoE information, but both always run on the same server in the same instance.
- groupchat – database for group chat
The collocation of databases is supported provided each are in a unique instance however the documentation tends to treat Group Chat as a separate entity and I believe this comes from the primary customer base within the financial vertical.
Oh and I do have Service Pack 2 applied, I realize Service Pack 3 has just recently released but we have not run the testing sufficient to provide a support statement on its use with the 2007 or R2 release.
This should be sufficient for me to start the planning and deployment of R2.