It was suggested to me that the solution does not require applications downtime.
However it does not seem to be working well in Azure SQL and databases with tables having more than 1 billion of small length records (often more than 2 billion)
The following command seems to be responsible for deadlock conditions during its run among other failures.
It was suggested to me that the solution does not require applications downtime.
However it does not seem to be working well in Azure SQL and databases with tables having more than 1 billion of small length records (often more than 2 billion)
The following command seems to be responsible for deadlock conditions during its run among other failures.
EXEC dbo.usp_AdaptiveIndexDefrag @Exec_Print=1 , @printCmds=1 , @rebuildThreshold=100 , @rebuildThreshold_cs=100 , @updateStats=1 , @scanMode = 'DETAILED' , @onlineRebuild=1 , @minFragmentation=5Has anyone experienced anything similar?