SQL Server Performance

The Ometa team makes great efforts to deliver a framework running with good performance on the databases it uses. Despite all of that, it remains possible to experience slow executing queries due to diverse circumstances.

In this section, a series of steps and guidelines are provided to diagnose such issues and a way to solve them.

Steps To Diagnose Slow Queries

When encountering performance degradation in relation to a potential SQL Server framework database, start with step 1, Identify Slow Queries, to examine the cause of the issue.

1. Identify Slow Queries
2. Reorganise Indexes
3. Update Statistics
4. Create Maintenance Plan

Missing Indexes

Warning

It might be tempting to create additional indexes in the framework databases in an attempt to speed up queries. However, Ometa advises NOT to do this without prior consultation. Only custom databases are supported.

The main reason for not adding indexes in the framework databases is that they may interrupt future software and additional database structure upgrades, as those indexes can block table changes among other things and cause the setup to fail.

The article Missing Indexes in Custom Databases provides some explanation on searching for missing indexes and how to add them on custom databases.