SQL Server Index Maintenance - OLA Hallengren Index Optimize
HTML-код
- Опубликовано: 10 сен 2024
- This video discusses the the OLA Hallengren Index Maintenance for SQL Server.
Available at: ola.hallengren...
00:08 OLA Hallengren Index Optimize
01:09 Installation Details
02:28 35 Parameter Listings
07:01 Sample Calls
If you would like to submit a question please submit it in the comments below!
Company Website
www.serverside-...
#SQLServer #Backup #OLAHallengren
This is a better update, thanks SQL
I wanted to only configure index reorganize using the olla hallengren. considering my database size is 10 TB should I keep the sort in tempdb option yes? Is there a way to reorganize the index without hampering the performance? How Can I configure olla hallengren scripts only for index reorganize even if the fragmentation level is above 30 %?
Thanks for your questions! I will try and follow up with a video, but here are some quick answers
should I keep the sort in tempdb option yes?
Depends on how much tempdp space you have available and how big your largest index is
Is there a way to reorganize the index without hampering the performance?
There is no free lunch, but you can use strategy to run index maint during off hours, split the work up, and use time limits!
How Can I configure olla hallengren scripts only for index reorganize even if the fragmentation level is above 30 %?
You can specify the same action for all thresholds. There is no rule that says you have to have a different action.
@FragmentationMedium = 'INDEX_REORGANIZE',
@FragmentationHigh = 'INDEX_REORGANIZE'
Hi ,
why Ola Hollagren index optimization job is filling up log space??
Hi - Index Maintenance does use a lot of log space because they generate a lot of changes to the index structures. Each index structure is modified as a single transaction, so depending on the indexes that were rebuilt that could require significant transaction log space. Transaction log space cannot be released to be reused until transactions are completed.