none
database ownership craziness RRS feed

  • Question

  • I'm a DBA supporting a Lync 2013 installation.

    After a few false starts we discovered that the installer insists on making the database owner 'sa' (by name).

    Our organization's, and I'm sure there are others, SQL security policy has us rename the built in 'sa' account.

    Thus the install fails, and I have to say this seems a like nuckleheaded move on the part of the installer dev team.

    In order to allow the installation to proceed, I created a disabled SQL Login called 'sa'.

    So the question now, can I safely change the owner to our renamed 'sa' without risk to future Lync service pack installations and patches?

     



    Wednesday, February 4, 2015 8:52 PM

All replies