Best practices for installing and configuring Enterprise Manager

Install Enterprise Manager on a machine that is separate from Intelligence Server.
Enterprise Manager must be installed on the same machine as MicroStrategy Command Manager.
The Enterprise Manager project can be in the same metadata as your other projects.
Create the statistics and Enterprise Manager repository in a database that is separate from a production data warehouse and MicroStrategy metadata. Intelligence Server can operate more efficiently if they are not in the same data warehouse.
Assign users to groups with the appropriate Enterprise Manager-related privileges.
- MicroStrategy Web Viewer group grants all the necessary privileges and permissions to view the out-of-the-box Enterprise Manager reports. Assign users to this group who need to view reports.
- In order to configure a project source and list projects to be monitored by MicroStrategy Enterprise Manager, the user must satisfy one of the following criteria:
  - User can be an Administrator user
  - User can be part of one of the following groups:
    - System Monitors
    - System Administrators (sub group of System Monitors)
    - Narrowcast System Administrators (sub group of System Monitors)
  - User can be part of the Everyone group with the following privileges granted:
    - Architect - Use Architect editors
    - Administration - Bypass all object security access checks
To ensure that you can successfully upgrade the Enterprise Manager project in the future, do not modify schema objects. Rather, make copies of the objects you want to modify and then modify the copies.
Upgrade to Enterprise Manager service packs when they become available. MicroStrategy includes your feedback in the service packs, including fixes to issues and additional enhancements.
After upgrading Enterprise Manager, delete any tables with the DELETE_ prefix that remain in the Enterprise Manager repository to maximize available space in the database.