Last updated: 2019-02-11

What is the Configuration Database?

The Configuration Database is a database hosted in SQL Server. During installation of Nodinite, a SQL Database prefixed IMConfig_ is created. This database has a different name for different environments (like IMConfig_Prod, IMConfig_Test etc.).

The Configuration Database is part of the Core Services which means that the installer helps you with both the installation and recurring updates. See Prerequisites for pre-installation related information.

Nodinite is designed to keep your environments performing well over time even though you add large amounts of data over time and the Configuration Database keeps track and holds statistics for all this data.

The following components interact and depends on the Configuration Database. Each of those other components may run with least privileges set making your environment more secure with the obvious side effect of added complexity and administration. The table in the Core Services Overview provides links to all SQL, Windows and firewall settings required for the other components. The 'Prerequisites' page further details this for the Configuration Database.

graph LR subgraph SQL Server roConfigDatabase(fal:fa-database Configuration database) --- |Linked Server| roLogDatabase(fal:fa-database fal:fa-database fal:fa-database Log databases) end subgraph Application Server roLogAPI(fal:fa-cloud-download Log API) --- roConfigDatabase roWebAPI(fal:fa-cloud Web API) roWebAPI --- roConfigDatabase roLoggingService(fal:fa-hdd Logging Service) --- roConfigDatabase roMonitoringService(fal:fa-watch-fitness Monitoring Service) --- roConfigDatabase end

Overview of Nodinite Core Services interacting with the configuration database

The Configuration Database has many stored procedures, table types, functions, and stores the Nodinite configuration in tables. All queries against Log Databases and BizTalk databases are executed as potentially remote queries using linked servers for access. The Linked Server must be properly configured, see Prerequisites for additional information.

Keep Users and SQL DBA's away from Nodinite databases At least you should be Aware, Nodinite is Always Aware! Even though Messages and Context Properties stored with Nodinite are encrypted you should limit your attack vectors and keep configuration data as secure as possible. Remember all operations should be performed from either the Web Client or the Web API since all changing operations are being Log Audited.

How do you know who read sensitive information? Nodinite helps you get aware

Single Server Example

The Configuration Database typically has at least the online Log Database running on the same SQL Server Instance.

graph LR subgraph SQL Server Instance roConfigDatabase(fal:fa-database Configuration database) --- |Linked Server| roLogDatabase(fal:fa-database fal:fa-database fal:fa-database Log databases) end

Overview of Nodinite Core Services interacting with the configuration database

Note: Linked server must be configured for access to all Log Databases, BizTalkDTADb and BizTalkMGMTDb, even if they are on the very same SQL Instance

Historical Databases stored on SQL Hotel

You do not have to delete 1 single transaction, Nodinite has the ability to log as much data for as long as you need. When the online Log Database grows to large or to old ('SizeToSplitDatabaseOn' and 'DaysToSplitDatabaseOn' System Parameters) a SQL DBA can move historical Log Databases to another SQL Instance as deemed necessary by your operating conditions. Disk volume is the #1 limiting factor, both from a performance perspective, but also you may end up having very large amounts of data to cope with.

roLogDatabase2(fal:fa-database fal:fa-database fal:fa-database Historical Log databases) end subgraph SQL Server roConfigDatabase(fal:fa-database Configuration database) --- |Linked Server| roLogDatabase(fal:fa-database Online Log database) roConfigDatabase --- |Linked Server| roLogDatabase2 end

Frequently asked questions

Common problems and FAQ for the Configuration Database not found on this page can be found in the troubleshooting page.


Next Step

Add or manage Log Databases

Log Databases