Description of the feature
It can be a new feature, or a change to an existing feature
Ola - I am comparing your approach on an Azure DW with that code provided by Yochanan Rachamim] in his AzureSQLMaintenance (https://techcommunity.microsoft.com/t5/user/viewprofilepage/user-id/246476) - What I like about Yochanan approach (even if not as feature rich as your code) is that he creates a Workload table of code to execute - that gives me an idea of when code may complete or is still outstanding and also provides the ability of re-Startability - I am running IndexOptimise on an Axure DW at moment and do not know if it is 1% finished or 99% finished ? At least with the Yochanan approach I know I have 1000 objects left to process etc - Have you considered this workload approach for your IndexOptimiser script - this is of course the only one I can run in Azure - BTW would call this via ADF it I put live.. rather than Azure Automation or Elastic Jobs Thanks Paul McMillan
Description of the feature It can be a new feature, or a change to an existing feature
Ola - I am comparing your approach on an Azure DW with that code provided by Yochanan Rachamim] in his AzureSQLMaintenance (https://techcommunity.microsoft.com/t5/user/viewprofilepage/user-id/246476) - What I like about Yochanan approach (even if not as feature rich as your code) is that he creates a Workload table of code to execute - that gives me an idea of when code may complete or is still outstanding and also provides the ability of re-Startability - I am running IndexOptimise on an Axure DW at moment and do not know if it is 1% finished or 99% finished ? At least with the Yochanan approach I know I have 1000 objects left to process etc - Have you considered this workload approach for your IndexOptimiser script - this is of course the only one I can run in Azure - BTW would call this via ADF it I put live.. rather than Azure Automation or Elastic Jobs Thanks Paul McMillan