Forum Discussion
Sujay1185
Feb 20, 2024Copper Contributor
Fragmentation report running for long time
We have client SQL database 2012 with 5 TB of data and we are trying to run the fragmentation report for index rebuild but the report query is running for almost 2 hours and we need to kill the sessi...
olafhelper
Feb 20, 2024Bronze Contributor
Sujay1185 , do you query via sys.dm_db_index_physical_stats? Then you can use the "mode" parameter to reduce the workload, see sys.dm_db_index_physical_stats (Transact-SQL) - SQL Server | Microsoft Learn => Scanning modes
- Sujay1185Feb 20, 2024Copper Contributor
olafhelper tried the below query against the user db
SELECT
dbtables.[name] AS 'TableName',
ISNULL(dbindexes.[name], 'Heap') AS 'IndexName',
indexstats.index_type_desc AS 'IndexType',
indexstats.avg_fragmentation_in_percent AS 'FragmentationPercent',
indexstats.page_count AS 'PageCount'
FROM
sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, Null) indexstats
INNER JOIN
sys.tables dbtables ON dbtables.[object_id] = indexstats.[object_id]
LEFT OUTER JOIN
sys.indexes AS dbindexes ON dbindexes.[object_id] = indexstats.[object_id]
AND indexstats.index_id = dbindexes.index_id
WHERE
indexstats.database_id = DB_ID() and indexstats.avg_fragmentation_in_percent > 50 and indexstats.page_count > 1000 and dbtables.[schema_id] =1
ORDER BY
indexstats.avg_fragmentation_in_percent DESC
For 6777 tables it was still running more than 1.5 hrs. Please let me know do we get the result further or any fine tune can be done.
Thanks,
Sujay
- olafhelperFeb 21, 2024Bronze ContributorAs I already wrote, use a different scanning mode.
- Sujay1185Feb 21, 2024Copper ContributorThanks it worked