I can suggest you take a back up from the DB and the ePO server as described on KB66616 before you upgrade your SQL server to a standard/enterprise version. If that upgrade is possible on the same server on the same instance then it should be OK for us too, juts ensure the instance is the same or if is a new instance then ensure those details are updated accordingly after the upgrade on the ePO config page, see "3 – Configure ePO and verify connectivity:" from the article below:
https://kc.mcafee.com/corporate/index?page=content&id=KB68427
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
When you install standard, I believe it installs its own instance rather than just upgrading sqlexpress (I could be wrong). In that case, it would then be the same process as moving the database to different location on same server and attaching it to the new sql instance. If you create a new sql server and move the database there, the procedure for both scenarios would be covered in https://kc.mcafee.com/corporate/index?page=content&id=KB68427
If you do create a new sql server, then I would highly suggest to download IISCrypto (free utility), run it and choose best practices and reboot. That will ensure the new sql server has the right ciphers and protocols that epo needs to connect to it. Be sure also to set up the account you are using to connect to the database in the new server or instance with appropriate permissions and default database as master.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA