Welcome to Community Server Sign in | Join | Help

OCS support for shared SQL Server

For organizations that want to consolidate multiple SQL instances on the same physical server, this configuration is now supported for Live Communications Server 2005 SP1 and Office Communications Server 2007.  Both of these products make use of SQL Server.  Previously, Microsoft recommended that Live Communications Server 2005 SP1 and Office Communications Server 2007 use SQL Server on a separate dedicated physical server.  As of this announcement, the database used in the Enterprise pool, the Archiving and CDR Server or the QoE (Quality of Experience) Monitoring Server can now share the same SQL Server with other application databases and remain a supported configuration by Microsoft Customer Support Services.

 This level of support does not imply that installing LCS or OCS server roles on the SQL Server is supported.  Installing LCS and OCS server roles collocated on the same physical server running SQL Server remains unsupported.  The physical server must be dedicated to running only SQL Server.

 The server running the Back-End Database can host other SQL applications, as long as they are hosted in different SQL instances; the SQL Server instance that hosts the Office Communications Server Back-End Database must be dedicated.

 If you are going to run other SQL applications on the same server as your Back-End Database, keep the following in mind:  

·         The Back-End Database must have separate dedicated physical drives for its databases and transaction logs.

·         The server must have enough RAM to cache the entire instance being using for Office Communications Server.

·         With this configuration, diagnosing performance issues will be more difficult.

·         This configuration is supported, but not recommended.

 To track the performance of the SQL instance used by the enterprise pool front-end servers, monitor the following performance counters:  

·         LC:USrv – 00 – DBStore\Usrv – 002 – Queue Latency (msec)

·         LC:USrv – 00 – DBStore\Usrv – 0 04– Sproc Latency (msec)  

For more details on how to monitor and interpret these counters, see the article “How can I tell if my server is healthy in less than 10 counters?” by Pauline Batthish: http://communicationsserverteam.com/archive/2007/09/10/9.aspx

 For an in-depth resource on Office Communications Server 2007 with detailed troubleshooting tips, refer to the Office Communications Server 2007 Resource Kit book available at Amazon, Barnes & Noble, and Quantum Books: http://www.microsoft.com/MSPress/books/10482.aspx

- Rui Maximo 

  Senior Technical Writer

 

 

 

 

Published Friday, January 18, 2008 12:00 PM by ocsteam
Filed Under: ,

Comments

 

AMorrissey said:

How much memory do we perceive a fully-used instance utilizing?
January 25, 2008 11:54 AM
 

pmorrissey said:

If we are not using Archiving, CDR or the QOE DB can we not use a shared instance of SQL? We have under 4000 users but are going with a Enterprise roll out of OCS. Will we really require these resources for this DB?
February 19, 2008 2:50 PM
 

kerberos said:

How do the configuration I need to create the Instance in my SQL Server ? I 'll use the OCS 2007 Enterprise with pools and I don't know to create the instance.

many thank's for all.
April 16, 2008 10:55 AM
 

klahir68 said:

In "Microsoft Office Communications Server 2007 Supportability Guide" there is mentioned that only SQL-Port 1433 is supported. You say that serveral sql instances are support, but each instance hast to run on it's own port.  In our enviroment we usually use other port numbers for security reasons. Further our sql instances are running under a special service account with adapted servicePrincipalName, e.g. "MSSQLSvc/server1.test.com:1465".
Is it supported to use an this configuration for ocs database instance?
June 24, 2008 7:10 AM
 

slaterun said:

I have setup Archiving for IM and meetins along with CDR's.  Using ArchivingCDR Reporter, I can get the call details.  How do I retrieve the IM and Meeting conversation details from the archive DB?
Thanks,
July 24, 2008 2:17 PM
Anonymous comments are disabled
Powered by Community Server, by Telligent Systems