Two OCS2k7 Enterprise pool point to one SQL2005 server RRS feed

  • Question


    Hi All,


    Here is my exsiting environment:


    AD Architecture:

    1. One forest and one child domain

       Eg. company.com (Root domain), abc.company.com (Child domain)


    OCS2k7 Enterprise Architecture:

    1. One OCS2k7 Enterprise edition in Root domain ( for example: In USA)

    2. One OCS2k7 Enterprise edition in Child domain (for example: In Hong Kong)


    SQL Server:

    1. One SQL server 2005 hosted on USA (Root domain) for serving USA OCS server

    2. One SQL server 2005 hosted on Hong Kong (Child domain) for servving Hong Kong OCS server


    For my question.

    I need to implment additional OCS2k7 Enterprise edition server on child domain, whether can i use exsiting SQL server in child domain or i should implement additional SQL server for the new OCS2k7 server?


    Because if i use the exising sql server, i'm afraid whether there is any impact or not after i implement additional OCS server, for example, will it override the existing database or not?


    Thanks a lot for your help.



    Sunday, November 2, 2008 3:36 AM

All replies

  • The Supportability Guide states that a dedicated SQL instance must be used for any OCS back-end databases, so I'd imagine that as long as you install an additional instance you can use the same SQL server for multiple pools.
    Sunday, November 2, 2008 4:18 AM
  • Hi Jeff,


    So, Do i need to use the same SQL instance for two OCS server pool in child domain for best practice? Is it impossible to use two SQL instance for two OCS server pool?


    Best Regards


    Sunday, November 2, 2008 5:23 AM
  • Let me rephrase, you must use a separate dedicated SQL instance for each OCS server pool.  The OCS databases of each pool will all have the same defined names and cannot be collocated on the same SQL instance.


    I would think that best practice would be to deploy dedicated SQL servers for separate pool as typical multiple pools are used in geographically dispersed or hot-standby DR scenarios and using the same SQL back-end server in these would not be advantageous.  For performance reasons separate SQL servers would defintely be the recommended approach.

    Sunday, November 2, 2008 12:45 PM
  • Hi Jeff,


    Thanks a lot for your recommendation. On the other hand, if i create two Enterprise pool in the same child domain with two SQL server for each pool, whether the presence state can be exchanged each other or not. For example.


    Pool01: (abc.company.com <--Child domain)

    IM: User A


    Pool02: (abc.company.com <--Child domain)

    IM: User B


    Is there any problem when User A change the state in IM such as "Away" status, whether the presence state of User A will be reflect on User B communicator? Thanks


    Best Regards

    Kenneth Chow

    Sunday, November 2, 2008 1:06 PM
  • Hi All,


    I am also looking for an answer to above question guys.


    Will the 2 pools on different SQL instances be able to communicate even?





    Wednesday, November 26, 2008 12:45 PM
  • Yes, if both pools are part of the same OCS deployment (same forest) then all communications would be natively supported (IM, presence, etc).
    Wednesday, November 26, 2008 2:11 PM

    Hi Jeff,


    Thanks for your reply.

    I am trying to setup a test lab using the same forest which I have "abc.com". I want to create a new pool in my enterprise pools which will be using a different sql instance on sql clustered server which has our sql instance/db in production. I have seen in the installation docuemnt in the "create enterprise wizard" that there is a window which asks you to reuse existing database. If you check the box "replace any existing database" , is this going to remove my db which is in production. The other option which if I did not select replace will be using an existing db which I do not want.


    I have read that I need to select OCS namespace while creating the pool. So can I use "abc.com" for my test lab in a different new pool or I have to define a new namespace.


    The OCS resource kit is not clear in explaining the above point.



    A. Zaher

    Wednesday, November 26, 2008 6:58 PM
  • As long as you point the second pool to a separate SQL instance then it can't overwrite your other pool's databases as they are in a completely different instance.



    Wednesday, November 26, 2008 8:33 PM