FAQ and Troubleshooting guide for Nodinite Configuration Database
The Nodinite Configuration Database is typically very small (<100MB). You can safely shrink this database at any time especially if the transaction log has grown large.
We recommend that you have the following settings for your Nodinite databases:
- Configuration Database should be set to use full recovery mode.
- Log Databases can be set to use simple recovery mode, at least when Nodinite is used together with BizTalk Server
You can read further about this in the following 'Microsoft SQL Server Recovery Models' article
There is just one, and only one Configuration Database per instance (environment) of Nodinite.
Nodinite was designed ground-up not to rely on, depend on, or use any Microsoft SQL Server jobs at all. All cleaning and heavy lifting is performed by our own processes for a total control.
There are no SQL Agent jobs (Yes you can use the free SQL Express with Nodinite!)
This topic is detailed in the prerequisite pages for each service.
The database is updated by the Update Tool during an Update of Nodinite. If this step fails, then we have documented how to manually update the Configuration Database in the 'ABOUT MANUALLY UPDATING THE CONFIGURATION DATABASE AND LOG DATABASES user guide.
Yes, this topic is detailed in the Moving Nodinite Databases
Yes, this topic is detailed in the Always on user guide.