Is the Index Maintenance default good for Ola Hallengren?

Is the Index Maintenance default good for Ola Hallengren?

However, the index maintenance defaults aren’t good for everyone. Here’s how they ship: CREATE PROCEDURE [dbo].

Which is better Ola Hallengren or SQL server maintenance?

If you’re a production database administrator responsible for backups, corruption checking, and index maintenance on SQL Server, try Ola Hallengren’s free database maintenance scripts. They’re better than yours (trust me), and they give you more flexibility than built-in maintenance plans.

How to configure Ola Hallengren’s maintenance scripts?

The defaults on some of these parameters are a little tricky: When an index is between @FragmentationLevel1 (5%) and @FragmentationLevel2 (30%), the scripts will perform the actions listed in @FragmentationMedium, in order. First it’ll try an index reorganize, which is an online operation.

Do you like Ola Hallengren’s statistics week scripts?

They’re less intrusive, but man, that LOB compaction stuff can really be time consuming. What I do like is updating statistics. Doing that can be the kick in the bad plan pants that you need to get things running smoothly again. I also really like Ola Hallengren’s free scripts for all your DBA broom and dustpan needs.

Which is part of Ola Hallengren’s SQL server maintenance solution?

The SQL Server Index and Statistics Maintenance part of Ola Hallengren’s solution consists of IndexOptmize stored procedure and IndexOptimize – USER_DATABASES agent job, that are created during the installation process.

Do you need configured schedule for Ola integrity check?

As all other jobs used in Ola’s Maintenance Solution, integrity check jobs also come without the configured schedules. These jobs can be used as such to run the integrity checks manually, but they do need the configured schedule if the solution needs to be automated.

When to do an offline rebuild in Ola Hallengren?

If the index’s design or your SQL Server edition doesn’t allow for that, it’ll perform the last resort – an offline index rebuild. When an index has higher fragmentation than @FragmentationLevel2 (30%), the scripts will try the actions listed in @FragmentationHigh – first an online rebuild, then if that’s not possible, an offline rebuild.