This article describes how to manually create and configure the ManageSoft database. The article gives a general overview, but does not go in to a level of detail to describe exact steps for all of ManageSoft's products or product versions. This Article obsoletes Article 100392.
The following procedure can be followed to set up a ManageSoft Deployment Manager database without needing to physically install the ManageSoft for administration servers Windows Installer MSI package on the computer running the database server.
This procedure assumes that Windows authentication is being used to authenticate access to the database.
Perform the following steps in a "development" environment. This is an environment in which the ManageSoft database will be installed through a normal installation of the ManageSoft for administration servers Windows Installer package in order to obtain files required for the "production" environment installation (see below).
The "development" environment is on a computer running SQL Server that can have a ManageSoft database configured.
- Install ManageSoft for administration servers on the "development" environment server, and select the options to install the data server components. Use the version of ManageSoft that you ultimately want to install in the "production" environment.
- After the installation has been completed, take a copy of the following files from Program Files\ManageSoft\Reporter\: mgsProcedures.sql, OpJobs.sql and perms.sql.
- On the ManageSoft for administrator servers CD image, take a copy of the following files from ManageSoft\Administration server\Migration\: schema.sql and OpQueries.sql
Perform the following steps in the "production" environment. This is the environment in the ManageSoft database is to be installed, but where the ManageSoft for administration servers Windows Installer package cannot be executed.
- Create MGS Data Readers and MGS Data Modifiers security groups to control read and write access to the ManageSoft database. Normally these security groups are local security groups on the database server, but they may be created as domain security groups if necessary (for example, due to policies which prohibit creation of local security groups on the database server).
- Create MGS Administrators and MGS Report Users domain security groups, and add them as members of theMGS Data Modifiers and MGS Data Readers security groups respectively.
- Edit the schema.sql script that was copied from the CD image, replacing DEFAULT_NAMING_CONTEXT andDEFAULT_FLAT_NAME with the correct values for the "production" environment.
- Edit the perms.sql script that was copied from the "development" environment to specify the correct names of the security groups for the "production" environment.
- Create a database named ManageSoft on the SQL Server instance with the settings
a. Recovery model: Simple
b. Collation: Latin1_General_CI_AS
c. Data and transaction log file locations: As desired to match database physical design
- Execute the SQL scripts in the following order to set up the database: