LCSKid

LCS and OCS Product Information

Deploying OCS R2 – SQL

Deploying OCS R2 – SQL

  • Comments 2
  • Likes

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 –

  1. poolbe - backend for the R2 pool
  2. archiving – Archiving of IM headers and/or body
  3. 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.
  4. 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.

Comments
  • Question for you with the named instances, did you have to do anything on the server that you are install OCS R2 on to get it to communicate with the named instance?  We deployed R2 succesfully into a lab but not with a named instance.  When we started with a named instance, we got an error when trying to add a server to the pool.  The error is:

    Unable to retrieve the wMI setting of MSFT_SIPLogSetting from pool backend 'server\namedinstance'.  Please ensure the backend database exists and is reachable.  (Error code: 0x800407D0)

    I'm no SQL guru so I'm pretty sure I'm just missing something.

    The named instance is on the same SQL server as an existing OCS R1 DB.  The R1 DB's are in the default instance.  Not sure if that is causing our issue.

  • Adam,

    I don't have the install UI in front of me but you typically supply the instance name or named instance during setup. I would connect to the SQL server with the proper admin tools (management/studio)and see what instance names exist, maybe there is a minor spelling mistake.

    The only other thing I could think of is folks try to deploy with firewalls or in different domains, we assume the same domain and no firewalls.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment