- 3 minutes to read

DatabaseMaintenance - System Parameter

Automate and optimize your Nodinite Log Database maintenance with the DatabaseMaintenance system parameter. This powerful feature keeps your platform running smoothly and reliably with minimal manual intervention, ensuring your integration landscape stays efficient and healthy.

  • ✅ Keep Log Databases compact and high-performing with automated maintenance
  • ✅ Automate reindex and shrink operations for optimal efficiency
  • ✅ Ensure reliability and business continuity without manual intervention
  • ✅ Minimize downtime with scheduled off-peak maintenance
  • ✅ Flexible control – Use Nodinite automation or your own SQL DBA processes

Nodinite is designed to perform scheduled maintenance jobs automatically, ensuring your integration platform remains efficient and reliable. However, SQL DBAs can choose to use alternative mechanisms for these tasks if preferred.

Use the System Parameter DatabaseMaintenance to control whether the Nodinite Logging Service performs these database maintenance jobs. Maintenance is scheduled to run between 03:00 AM and 04:00 AM, with the actual start time depending on other system activities. Cleanup operations have lower priority and execute after higher-priority tasks are completed.

System Parameter Name Data Type Values/Example Comment
DatabaseMaintenance boolean true/false Default = true. When true, Nodinite performs scheduled database maintenance on Log Databases.

This feature was introduced in version 3.0.

Important Recommendation

If you run your own SQL maintenance jobs or third-party tools against the same SQL Server instance, make the ownership model explicit:

  • Set DatabaseMaintenance to false only if your jobs are intended to maintain Nodinite Log Databases.
  • Recommended approach: exclude Nodinite databases from your own maintenance jobs and keep DatabaseMaintenance set to true so Nodinite applies its built-in maintenance rules.

This avoids overlapping reindex/shrink operations, reduces contention, and keeps maintenance behavior predictable.

Example: Exclude Nodinite databases in IndexOptimize

If you use Ola Hallengren's IndexOptimize and all Nodinite databases share the Nodinite prefix, exclude them with a wildcard pattern:

EXECUTE dbo.IndexOptimize
    @Databases = 'USER_DATABASES,-Nodinite%',
    @FragmentationLow = NULL,
    @FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
    @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
    @UpdateStatistics = 'ALL';

This excludes every database with a name that starts with Nodinite (for example Nodinite_DEMO_Config and Nodinite_Log_DEV_20241108).

Active database

  • Reindex – Performed if the reported fragmentation count exceeds 10%.

Archive databases

  • Reindex – Performed if the reported fragmentation count exceeds 10%.

  • Shrink – Attempts to shrink the database to return allocated disk space to the system. Regular backups are a prerequisite.

    The shrink operation is a privileged task requiring the account running the Logging Service to have the sysadmin role.

For guidance on installation-time rights, first database creation, and policy-aligned fallback models, see SQL Server Sysadmin Requirements.

Configuration example

Field Data Type Description
Enabled Boolean (true/false) When true, Nodinite performs database maintenance jobs. When false, it does not.

Frequently Asked Questions

Find more solutions and answers in the Nodinite System Parameters FAQ and the Troubleshooting user guide.

How do I change the value?

Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.

Do I need to restart anything?

If this system parameter is set to true, the Logging Service performs the maintenance jobs. If you change this value, you do NOT need to restart anything. Changes are effective almost immediately, ensuring minimal disruption and maximum agility.

Next Step

Administration