Тёмный

Index Rebuilding & Stats Gathering: Best Practices for Database Administrators. 

Anish kumar
Подписаться 683
Просмотров 6 тыс.
50% 1

Rebuilding an index means deleting the old index replacing it with a new index. Performing an index rebuild eliminates fragmentation, compacts the pages based on the existing fill factor setting to reclaim storage space, and also reorders the index rows into contiguous pages.
You must gather statistics on a regular basis to provide the optimizer with information about schema objects. New statistics should be gathered after a schema object's data or structure are modified in ways that make the previous statistics inaccurate.
Gather Stats job is the default job running in Oracle Database for collecting the most used tables stats automatically. Oracle monitor the most DML tables with help of DBA_TAB_MODIFICATIONS view which stores information about the inserts, deletes, and updates to a table.
For more Information Visit:
asrblogger.com/
For More Detailed Info:
asrblogger.com/how-to-decide-...
asrblogger.com/basic-concepts...
asrblogger.com/index-and-stat...
Join Telegram : t.me/asrBlogger
Scripts from Github : github.com/anishs10/db-scripts
#oracledatabase #oracledatabasetutorial #performancetuning #databasetuning #performanceoptimization #asrblogger #asrbloggerdba

Опубликовано:

 

5 май 2023

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 11   
@Karankumar-zy3pf
@Karankumar-zy3pf Год назад
Thank you Anish sir. Your videos are really informative.
@avnishsingh5861
@avnishsingh5861 Год назад
Very insightful baba... Hope to collab with you soon
@vickywankhade6122
@vickywankhade6122 3 месяца назад
Dba_indexes
@balajichandramohan5117
@balajichandramohan5117 Месяц назад
Hi there, how to find the index is in use or not.
@anishkumarvideos
@anishkumarvideos 23 дня назад
Using V$OBJECT_USAGE The V$OBJECT_USAGE view keeps track of whether an index has been used since it was last monitored. You need to start monitoring an index first: Start Monitoring an Index: ALTER INDEX index_name MONITORING USAGE; Query the Usage: After some time, you can check if the index has been used: SELECT index_name, table_name, monitoring, used, start_monitoring, end_monitoring FROM V$OBJECT_USAGE WHERE index_name = 'INDEX_NAME'; Stop Monitoring an Index: ALTER INDEX index_name NOMONITORING USAGE; Hope it helped !! :)
@balajichandramohan5117
@balajichandramohan5117 23 дня назад
@@anishkumarvideos Thank you
@jerkmeo
@jerkmeo Месяц назад
nice video!!
@anishkumarvideos
@anishkumarvideos 23 дня назад
Thanks for the visit :)
@kirankumar-np7tc
@kirankumar-np7tc 8 месяцев назад
What is estimate percentage and auto sample size
@anishkumarvideos
@anishkumarvideos 8 месяцев назад
There are 2 situations where AUTO_SAMPLE_SIZE can occur: If, during processing, the procedure determines that the returned information for the sample is insufficient for accurate access path selection, the sample can be increased by a factor of ten and restarted. For example, if AUTO_SAMPLE_SIZE started with around 5500 rows, when the procedure determines that the sample is insufficient then it will then increase the sample (for example to 55000) and restart. If this is insufficient, it increases by another factor of 10, and so on. However, if the sample size exceeds 25% of the table size, it will switch automatically to COMPUTE (100% sample). There is a case where the sample taken is sufficient for accurate statistics, but the number of rows is judged to be poorly estimated (either for the table or an index). Sample_size is set at the lower value, but then dbms_stats will take an accurate row count by using SELECT COUNT(*) from the table and index. As well as setting the num_rows, dbms_stats will also set the sample_size to this value (as this is the number of rows sampled to produce num_rows). In this case, the sample_size, although accurate for the last operation, is misleading as far as the full sample taken for the other gathered statistics. You expect the sample size from: select table_name, last_analyzed, sample_size, num_rows from dba_tables where table_name = '.........';
Далее
Why Rebuild Indexes? | #dailyDBA 20
30:50
Просмотров 25 тыс.
SQL Index |¦| Indexes in SQL |¦| Database Index
9:57
SQL Server Update Statistics with Full Scan
11:25
Просмотров 3,3 тыс.
Microservices with Databases can be challenging...
20:52
How do SQL Indexes Work
12:12
Просмотров 581 тыс.
Oracle statistics | Database Performace tuning
6:30
Просмотров 19 тыс.