Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

A dedicated or pre-existing SQL server will have to be commissioned/made available to host the Enterprise Commander data. This server will need to be a SQL Server 2012 or higher and will need to be set up with:

  • Mixed mode authentication
  • Local account with privileges to create a DB and read and write to that DB

SQL Server Schema set up

The Schema to host the Enterprise Commander data will need to be set up as follows:

  1. Create a login user called ER_USER for your SQL server. This account can be an AD account or a local account on the SQL server.
  2. Create a new Database called ER_COMMANDER and leave the Owner as <default>.
  3. Create a schema called 'ENGINEROOM'.
  4. In the ER_COMMANDER database create a new user for the database called ER_USER (note: this user is different to the ER_USER created to log into the SQL server).
  5. Map the Database user ER_USER to the SQL login user ER_USER and assign the default schema as 'ENGINEROOM'. On the Membership view, select dbo_owner.

Now that the pre-requisite services and SQL server have been set up, you are now ready to install Enterprise Commander.

  • No labels