4 Replies Latest reply on May 10, 2016 6:33 PM by Peachy Velasco

    Does Uniprint 9.0 R2 support the use of SQL 2014?

    Andrea Clark Adventurer

      Hello Pharo Community,

       

      I'm a newbie to Pharos, so please be gentle. :-) My organization is about to set up a test environment for Uniprint 9.0 R2. We are spec'ing out the requirements for the environment and our DBA has a couple of questions concerning supported SQL versions and permissions requirements.

       

      Is Uniprint 9.0 R2 supported with SQL 2014, if not, is there an ETA for it's support?

       

      We will be deploying the Pharos services on a dedicated test and separate production server, with separate SQL backend servers. The documentation indicates that the installation tech will need the SA ID and password with local administrator rights to all servers, including the database servers.

       

      What specific database permissions are required for the Pharos database userID?

      Why would it be necessary for the Pharos installation tech to have local administrator rights on the dedicated database server that is managed separately by a DBA team?

       

      Thank you in advance.

       

      Andrea Clark

      Windows Server and Application Administrator

      University of Texas at Dallas

        • Re: Does Uniprint 9.0 R2 support the use of SQL 2014?
          Steven English Guide

          Good Afternoon Andrea Clark,

           

          The reason that the Pharos Installer requests the SA username and password is so that the installer process can...

          1. Create the mixed mode SQL security logon ID that Pharos will use for day to day operations (new installs)
          2. Create the database itself and assign the user account from step 1 as the owner (new installs)
          3. Or if doing an upgrade, it wants it to run update queries against the database during the upgrade process so that it is of the correct version

           

          When accessing a SQL server that houses a number of other databases, it is common for the DBAs to prefer to not share credentials.  This is not a problem, as it is easy enough to either have your DBA enter the credentials so that the installation tech is kept in the dark, or the DBA can manually take the steps that the installer would have done.  This involves creating the appropriate SQL security login account, setting permissions on that account, attaching the database with the newly created account as the database owner.  The server role for said user is public, and it needs to be granted permission to connect to the database engine and login to SQL.  The user's default database should be set to 'pharos' once it has been attached.

           

          I am inferring from your question that the production SQL server is on a separate machine/cluster from the ones that will be running the principal Pharos service.  Assuming this is the case, no local administrative privileges would be needed on the SQL box - just a set of SQL credentials that have the sys admin permission level unless the steps are manually taken as described in the previous paragraph.  Please note that the installation of Pharos itself should be installed by a Windows account with administrative privileges - preferably the local admin since it is less likely to have GPOs or other restrictions on it.

           

          Regards,

          Steven

            • Re: Does Uniprint 9.0 R2 support the use of SQL 2014?
              Andrea Clark Adventurer

              Our DBA has concerns about inconsistencies in the 9.0 R2 Planning and Installation Guide. On page 23 under Database Requirements, It lists SQL 2014. However, on page 43 under heading SQL Server for Pharos, there is no mention of SQL 2014. Nor is there reference to SQL 2012 or 2014 on page 44 for the SQL Administrator (SA) account login rights check list.

               

              Is 2014 supported?

              Are there different requirements for the older versions of SQL?

              What are the specific requirements for SQL 2014, if supported?

              What are the specific requirements for SQL 2012 R2, if 2014 is not supported?