Pre-create OCS databases?

Všechny reakce

• 12. srpna 2009 12:23

  Moderátor

   

   
  

  0

  Hi:

  According to your issue, it is depend what edition you want to deploy.

  1.     If you deploy the Enterprise Edition server, you must install a SQL server as the Back-End Database. About the Enterprise Edition Process you can refer to below link:

  http://technet.microsoft.com/en-us/library/dd425257(office.13).aspx

  2.     If you deploy the Standard Edition server, the Setup automatically installs Microsoft SQL 2005 Express Edition with SP2 for the back-end database. About the Standard Edition server Deployment Process you can refer to below link:

  http://technet.microsoft.com/en-us/library/dd441316(office.13).aspx

   

  Hope this helpful!

  Regards!

  
  
   
• 12. srpna 2009 12:30

  Moderátor

   

   
  

  0
  Matt,
  
  I have not tested that before, but if you create the databases ahead of time and OCS 'reuses' the exiting ones then it may not perform configuration tasks on them (e.g. security setting) any installatino may fail.
  
  What is the reason you are not able to let the OCS setup wizard perform those tasks itself?

  ---

  Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
   
• 12. srpna 2009 13:24

   

   
  

  0

  Gavin,
  
  We'll be deploying Enterprise edition.  I've already reviewed those materials but there is no mention to pre-creating the databases.

   
• 12. srpna 2009 13:26

   

   
  

  0
  Jeff,
  
  Company protocol.  The person setting up the OCS server does not have DB permissions over the SQL cluster.  When I submitted the change request for database space they misread my request and had the databases pre-created.  A change now would require a new change request and delay the project a week or more and we are running out of time.
   
• 12. srpna 2009 23:48

  Moderátor

   

   
  

  0
  Matt,
  
  I checked with the product team and there is currently no way to manually create and configure the databases for OCS.  The process must be handled by the setup wizard, as it's not just empty databases that are created but permissioning and other undocumented settings as well.
  
  If you are in a major time crunch one option you have is to stand up another SQL server (virtual would do) and get OCS deployed and working.  Then move the databases to the production server once all the red-tape has been cut.  It's not ideal, but you don't have much in the way of options at this point.

  ---

  Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS

  • Označen jako odpověď Matt.WadeMicrosoft Employee 13. srpna 2009 1:25
  •  
   
• 13. srpna 2009 1:25

   

   
  

  0
  Jeff,
  
  Thanks for the information, though I have to say that the idea of there being undocumented settings is down right scary.  Now, if I were to say exactly what you just said my client would most likely have a heart attack.  Well, time to break the news and see if we can't push this change through quick.  Fortunately, my original change request clearly stated that the DBs needed to be setup automatically.  The DBA "skimmed" through the request and "assumed" it needed to be created manually.  :)