- 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.

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. The number of Log Databases depends on your specific configuration and usage. Each Log Database is designed to store logs and monitoring events for different environments or applications.

Are there any SQL Jobs?

No, Nodinite does not ship with, or make use of SQL Jobs for managing Log Databases. Instead, it relies on its own processes to handle data management tasks such as cleaning and archiving logs. This design choice allows for greater control and performance optimization. Nodinite is designed without any dependency on SQL Jobs. All cleaning and heavy lifting is performed by our own processes for total control and fine-tuned performance.

What is stored in the Log Database?

Nodinite Log Databases store all Nodinite Log Events and Monitoring Events generated by your integration solutions. 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.

For more information on configuring Always On for Nodinite Log Databases, please refer to the Always On user guide.

Next Steps

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 at support@nodinite.com