What is the Nodinite Configuration Database?
The Nodinite Configuration Database is the secure, high-performance backbone of your integration environment. Hosted in your SQL Server instance, it provides robust configuration, auditing, and management for all Nodinite Core Services.
✅ Centralize and secure all configuration and system parameters
✅ Ensure long-term performance and reliability, even as data grows
✅ Enable robust auditing and compliance with full change tracking
✅ Simplify management for system integration experts and IT teams
The Nodinite Installer automatically creates a new SQL Database prefixed NodiniteConfig_, with unique names for each Environment (such as NodiniteConfig_Prod, NodiniteConfig_Test, etc.).
As part of the Core Services, the Configuration Database benefits from seamless installation and regular updates via the installer. For pre-installation details, see Prerequisites.
Nodinite is engineered to keep your environments running smoothly, even as your data grows. The Configuration Database efficiently stores statistics and configuration data indefinitely, ensuring long-term performance and reliability.
Multiple components interact with and depend on the Configuration Database. Each component can be configured with least-privilege access, enhancing security while introducing some additional administrative complexity. The Core Services Overview table provides links to all required SQL, Windows, and firewall settings. The 'Prerequisites' page offers further details specific to the Configuration Database.
Overview of the Nodinite Web Applications and Services interacting with the configuration database.
The Configuration Database contains many stored procedures, table types, and functions, and stores all Nodinite configuration in dedicated tables. All queries against Log Databases and BizTalk databases are executed as potentially remote queries using linked servers. Ensure the Linked Server is properly configured—see Prerequisites for more information.
Keep Users and SQL DBAs away from Nodinite databases!
Nodinite is always aware—while messages and context properties are encrypted, you should minimize attack vectors and keep configuration data secure. All operations should be performed via the Web Client or Web API to ensure every change is Log Audited.
How do you know who accessed sensitive information? Nodinite helps you stay aware and compliant.
Single Server Example
The Nodinite Configuration Database typically resides alongside the current online Log Database on the same SQL Server Instance.
Overview of Nodinite Core Services interacting with the configuration database.
Important
A Linked Server must be configured for access to all Nodinite Log Databases. For Microsoft BizTalk Server, a Linked Server is also required for BizTalkDTADb and BizTalkMGMTDb.
Historical Databases Stored on SQL Hotel
With Nodinite, you never have to delete a single transaction! Log as much data as you need, for as long as you need. When the online Log Database grows too large or too old (see 'SizeToSplitDatabaseOn' and 'DaysToSplitDatabaseOn' System Parameters), a SQL DBA can move historical Log Databases to another SQL Instance as needed. Disk volume is the primary limiting factor—both for performance and for managing large data volumes.
Frequently Asked Questions
Find solutions to common problems and explore the Nodinite Configuration Database FAQ in the Troubleshooting user guide.