2 Replies Latest reply on Sep 30, 2013 8:29 AM by rackroyd

    New ePO




      We currently have existing epo 5.0 and DB servers both are seperate physical server in main office (25K users).


      however our branch office (5K users) purchased there own epo 5.0 server and we are thinking if we can co-locate or use the existing DB in the main office..is this possible??


      can the DB communicate into two seperate epo instances?


      Thanks in advance

        • 1. Re: New ePO
          Laszlo G

          Hi yzerman10, you can import the branch office DB to your local SQL server and then set the branch office ePO to connect to the new DB location.


          But be advise that you'll need a huge broadband connection between the branch office ePO server and your local SQL database ¡

          • 2. Re: New ePO

            So long as each ePO has its own instance it does not matter if they are on the same Sql server or not.

            As stated what really matters here is the connection speed from the ePO server to the DB instance and that the DB server spec is up to the job of running multiple instances of ePO databases.


            If your Sql server is in a separate physical location after the move then you will need a connection speed equivalent and stable enough as if it were still on the same network otherwise it will become a significant performance bottleneck. Data exchange between ePO server & Sql DB is constant  and heavy. It really needs a good link between the two.


            If you can't meet that criteria then don't make the consolidation.