Database Deployment Options
This section describes the different options available for the Neurons for ITSM databases.
•About the Databases Used in Neurons for ITSM
•Option D1: Separate Database Servers (Recommended and Best Practice)
•Option D2a: Single Database Server (Best Practice)
•Option D2b: Single Database Server
•Option D3: Single Configuration Database on a Single Database Server
•Option D4: Multiple Configuration Databases on a Single Server
•Option D5: Multiple Configuration Databases on Multiple Servers
•Option D6: Single Configuration Database on Separate Database Servers (for MSPs)
•Option D7: Multiple Configuration Databases on Separate Database Servers (for MSPs)
About the Databases Used in Neurons for ITSM
The following are the databases used in Neurons for ITSM:
•configuration database (ConfigDB)
•Neurons for ITSM application database (IvantiSM)
•Neurons for ITSM reporting database (ReportDB). This database is used for the reporting feature. See Reporting Services Deployment Options for more information.
•Metrics cache database (Metrics Cache DB). This database is used to cache the run-time state of the schedule jobs. Only one metrics cache database is needed in each isolated landscape. For example, if the configuration database and the Neurons for ITSM application database are hosted on the same database server, your deployment only needs one metrics cache database.
In addition, there are generally three instances for each tenant:
•Staging
•UAT
•Production
Each tenant instance, Staging (development), UAT (Test) and Production, can have its own database instance or server. These are called:
| Database | Description |
|---|---|
| IvantiSM | Application database for production |
| IvantiSM-STG | Application database for staging (development) |
| IvantiSM-UAT | Application database for UAT (testing) |
| IvantiSM-Dev | Application database for staging (development) and UAT (testing) |
| ConfigDB | Configuration database for production |
| ConfigDB-STG | Configuration database for staging (development) |
| ConfigDB-UAT | Configuration database for UAT (testing) |
| ConfigDB-Dev | Configuration database for staging (development) and UAT (testing) |
| ReportServer | Report database for production |
| ReportServer-STG | Report database for staging (development) |
| ReportServer-UAT | Report database for UAT (testing) |
| ReportServer-Dev | Report database for staging (development) and UAT (testing) |
The advantage of hosting a database on its own server is that it ensures security by isolating the production landscape. It also enhances performance. When you make multiple changes or upgrades to the staging or UAT landscapes, you do not want that to affect the performance of the production landscape. Separating the different databases makes it easier to upgrade the systems, because when you upgrade the systems you have to shut them down and that affects users in the production landscape.
The advantage of hosting everything on one server is that you save money by only having to purchase and administer one server and one Microsoft SQL Server license.
Diagram Conventions
The following conventions are used in the diagrams:
•A line item is considered a database. There can be many databases within one database engine instance.
•A barrel is considered a database engine instance. It can contain multiple database instances.
•A square or rectangle around something means it is on one server (machine). Each server can potentially host multiple database engine instances.
Diagram Conventions
Option D1: Separate Database Servers (Recommended and Best Practice)
In this deployment, there are two separate database servers. One is for the production landscape and the other is for the staging and UAT landscape. The staging and UAT servers share a configuration database.
Example of Separate Database Servers
Option D2a: Single Database Server (Best Practice)
In this deployment, there is a single database server and one configuration database (ConfigDB-Dev).
Example of Recommended Single Database Server
Option D2b: Single Database Server
In this deployment, there is a single database server and either no configuration database or two configuration databases (ConfigDB-STG and ConfigDB-UAT).
Example of Alternative Single Database Servers
Option D3: Single Configuration Database on a Single Database Server
In this deployment, there is one configuration database for the production landscape and another configuration database shared between the staging and UAT landscapes.
Example of Separate Database Engine Instances on a Single Database Server
Option D4: Multiple Configuration Databases on a Single Server
In this deployment, there are separate configuration databases for the production landscape, the staging landscape, and the UAT landscape.
Example of Multiple Configuration Databases on a Single Server
Option D5: Multiple Configuration Databases on Multiple Servers
In this deployment, there are separate configuration databases for the production landscape, the staging landscape, and the UAT landscape and separate instances.
Example of Multiple Configuration Databases on Multiple Servers
Option D6: Single Configuration Database on Separate Database Servers (for MSPs)
A Managed Service Provider (MSP) is a service partner who provides Neurons for ITSM for multiple tenants or outside customers.
In this deployment, there is a single configuration database shared between landscapes.
Example of a Single Configuration Database on Separate Database Servers
Option D7: Multiple Configuration Databases on Separate Database Servers (for MSPs)
In this deployment, there are separate configuration databases for the production landscape, the staging landscape, and the UAT landscape and separate instances.
Example of Multiple Configuration Databases on Separate Database Servers
