- 4 minutes to read

FAQ and Troubleshooting Guide for Nodinite Log Databases

Quickly resolve issues and optimize your Nodinite Log Databases with this comprehensive FAQ and troubleshooting guide. Here you'll find answers to common questions, best practices, and expert support options to keep your integration data secure, high-performing, and compliant.

What you'll find on this page:

  • ✅ Sizing and performance tips for Log Databases
  • ✅ Recommended SQL Server recovery models
  • ✅ High availability and migration guidance
  • ✅ Direct access to Nodinite support

How large is the Log Database?

The size of the Nodinite Log Database can vary based on your usage patterns, but it is generally designed to be efficient and scalable. The Log Databases are typically sized between 0–100 GB. The online Log Database is split when it grows past SizeToSplitDatabaseOn (default 50 GB) or gets older than DaysToSplitDatabaseOn; see How a new Log Database is created.

What Recovery Model should I have?

Nodinite Log Databases can use different SQL Server recovery models depending on your needs. The Configuration Database should always use full recovery mode to ensure all changes are logged and can be restored.

The LogDatabaseRecovery system parameter controls the recovery model for new Log Databases. For Always On configurations, this must be set to FULL.

A Log Database might need to be set to SIMPLE when Nodinite is co-hosted with the SQL Server instance in use with BizTalk Server.

You can read further about this in the 'Microsoft SQL Server Recovery Models' article.

How many Log Databases are there?

There is no fixed number of Log Databases in Nodinite. Each environment has exactly one online Log Database and any number of archive Log Databases: data is partitioned over time, and a new online Log Database is created each time a split limit is reached. Administrators see the list under Administration › Settings › Log Databases.

Are there any SQL Jobs?

No, Nodinite does not ship with, or make use of SQL Jobs for managing Log Databases. The Logging Service handles cleanup, splitting, and maintenance itself; the DatabaseMaintenance System Parameter controls nightly reindexing and the shrinking of archive Log Databases.

What is stored in the Log Database?

Nodinite Log Databases store the Log Events, message bodies, and context properties logged from your integration solutions, and the Monitoring Events (the state change history of your Resources) that the Monitoring Service writes and purges after DaysToKeepMonitorEvents days. This includes detailed information about message processing, errors, and system performance. The data is encrypted and compressed to ensure security and efficiency.

Can I move the Log Database to another SQL Instance?

Yes, you can move the Log Database to another SQL Instance. However, this process requires careful planning and execution to ensure data integrity and continuity. You can find detailed instructions in the Moving Nodinite Databases user guide.

Does the Log Database support high availability SQL Servers (Always On)?

Yes, Nodinite Log Databases can be configured to support high availability using SQL Server Always On Availability Groups. This setup ensures that your log data remains accessible and resilient in case of server failures.

Important

When using Always On Availability Groups, the LogDatabaseRecovery system parameter must be set to FULL recovery mode. This is required for SQL Server to maintain the transaction log chain necessary for AOAG synchronization.

When the Logging Service creates a new Log Database on an availability group, it uses the backup share in the AvailabilityGroupBackupPath System Parameter. For more information on configuring Always On for Nodinite Log Databases, please refer to the Always On user guide.

Contact our support

If you still have any questions or have trouble with the Log Databases, don't hesitate to get in touch with us, read more on the Support page.

Next Steps