FAQ and Troubleshooting guide for Nodinite Configuration Database
The 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 SQL Jobs at all. All cleaning and heavy lifting is performed by our own processes for total control. There are no SQL Agent jobs (Yes you can use the free SQL Express with Nodinite!)
Yes, but you must update the following configuration files: |Core Service|Configuration file|Restart required|Comment| |---|---|:---:|---| | Monitoring Service| Nodinite.Service.MonitoringServiceHost.exe.config|Yes|Change the connectionString content| | Logging Service|Nodinite.Service.LoggingServiceHost.exe.config|Yes|Change the connectionString content| | Web API|web.config|Automatic when saving web.config|Change the connectionString content| | Log API|web.config|Automatic when saving web.config|Change the connectionString content|
<connectionStrings> <add name="NodiniteConfigDatabase" connectionString="Data Source=localhost;Initial Catalog=NodiniteConfig_Dev;Integrated Security=SSPI" providerName="" /> </connectionStrings>
Example connectionString within configuration file
This topic is detailed in the Always on user guide.