FAQ and Troubleshooting guide for Nodinite Configuration Database
This page provides answers to the most common questions and troubleshooting scenarios for the Nodinite Configuration Database. Whether you are a systems integration expert or evaluating Nodinite for your organization, you'll find practical guidance and expert tips to ensure a seamless experience.
✅ Learn about database sizing, recovery models, and SQL job requirements
✅ Get best practices for backup, restore, and high availability
✅ Access expert support and step-by-step troubleshooting resources
✅ Simplify management and ensure compliance for your integration landscape
How large is the configuration database?
The Nodinite Configuration Database is typically very small (less than 100MB). You can safely shrink this database at any time, especially if the transaction log has grown large. This compact size ensures efficient management and minimal storage requirements, making Nodinite a lightweight yet powerful solution for your integration needs.
What Recovery Model should I have?
We recommend the following settings for your Nodinite databases:
- Set the Configuration Database to use full recovery mode for robust backup and restore capabilities.
- Set the Log Databases to use simple recovery mode, especially if Nodinite is used with Microsoft BizTalk Server.
For more details, see the official 'Microsoft SQL Server Recovery Models' article.
How many configuration databases are there?
There is only one Configuration Database per instance (environment) of Nodinite. This design simplifies management and ensures consistency across your integration landscape.
Are there any SQL Jobs?
Nodinite is designed from the ground up not to rely on, depend on, or use any Microsoft SQL Server jobs. All maintenance and data management are handled internally by Nodinite processes, giving you total control and reducing operational complexity.
Note
There are no SQL Agent jobs (Yes, you can use the free SQL Express with Nodinite!)
What is stored in the Configuration Database?
All configurable content is stored here, including the Repository Model, Log Views and their related entities, Monitor Views and related entities, and more. This centralization streamlines configuration and enhances visibility for system integration experts.
What SQL Server access rights do the Nodinite related services require?
Access rights requirements are detailed in the prerequisite pages for each service. Please refer to those guides to ensure proper configuration and security.
How do I update the configuration database?
The database is updated by the Update Tool during an Update of Nodinite. If this step fails, we provide comprehensive documentation on how to manually update the Configuration Database in the 'ABOUT MANUALLY UPDATING THE CONFIGURATION DATABASE AND LOG DATABASES' user guide.
Can I move the configuration database to another SQL Instance?
Yes, you can move the database. Detailed instructions are available in the Moving Nodinite Databases user guide.
Does the configuration database support high availability SQL Server (Always On)?
Yes, Nodinite fully supports high availability scenarios, including SQL Server Always On. For more information, see the Always-on user guide.
Contact our support
If you have any questions or encounter issues with the Configuration Database, our expert support team is here to help! Reach out to us at support@nodinite.com for fast, knowledgeable assistance.