Versions Compared

Old Version 11

changes.mady.by.user Unknown User (6092af18a56f2f006f392eb0)

Saved on

compared with

New Version 12

changes.mady.by.user Unknown User (6092af18a56f2f006f392eb0)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. If you want to use the latest version of SQL Compliance Manager, Upgrade to this build.
  2. Disable auditing on a SQL Server at the server level.
  3. Stop the SQL Compliance Manager Agent service. Use the Microsoft Services administrative tool to stop the SQL Compliance Manager Agent service (SQL Compliance Manager Agent) running on the Collection Server computer.
  4. Stop the Collection Server service. Use the Microsoft Services administrative tool to stop the Collection Server service (SQL Compliance Manager Collection Service) running on the Collection Server computer.
  5. Upgrade SQL Server on the Collection Server computer.
  6. Restart the Collection Server service. Use the Microsoft Services administrative tool to restart the Collection Server service (SQLcompliance Collection Service) running on the Collection Server computer.
  7. Restart the SQL Compliance Manager Agent service. Use the Microsoft Services administrative tool to restart the SQL Compliance Manager Agent service (SQL Compliance Manager Agent) running on the Collection Server computer.
  8. If you upgraded SQL Compliance Manager to the latest version, also upgrade the SQL Compliance Manager Agent remotely. 
  9. Upgrade the SQL Server software on the computers hosting your audited instances.
  10. Begin auditing any new SQL Server instances.


Scroll pdf ignore

SQL Compliance Manager audits all activity on your server. Learn more > >

IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal

Scroll Pagebreak