Database Deployment Options

this section describes the different options available for the databases about the databases used in neurons for itsm docid\ h8xefagya8j 286x6q747diagram conventions docid\ h8xefagya8j 286x6q747option d1 separate database servers (recommended and best practice) docid\ h8xefagya8j 286x6q747option d2a single database server (best practice) docid\ h8xefagya8j 286x6q747option d2b single database server docid\ h8xefagya8j 286x6q747option d3 single configuration database on a single database server docid\ h8xefagya8j 286x6q747option d4 multiple configuration databases on a single server docid\ h8xefagya8j 286x6q747option d5 multiple configuration databases on multiple servers docid\ h8xefagya8j 286x6q747option d6 single configuration database on separate database servers (for msps) docid\ h8xefagya8j 286x6q747option d7 multiple configuration databases on separate database servers (for msps) docid\ h8xefagya8j 286x6q747 about the databases used in neurons for itsm the following are the databases used in configuration database (configdb) application database (ivantism) reporting database (reportdb) this database is used for the reporting feature see reporting services deployment options docid\ s8cbrq485ram2mpethssq 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 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 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