Guidance on running `3_job_AdaptiveIndexDefrag` on Azure SQL

Open
#298 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, sql

Research direction

Start by reading 3_job_AdaptiveIndexDefrag.sql and usp_AdaptiveIndexDefrag.sql, then compare their database context and references to Azure SQL capabilities. Check how references such as msdb.dbo.sysjobs apply in Azure SQL. Done means the repository documents the required context and a clear way to create or run the job in Azure SQL.

Written by the indexing model from the issue text.

Description

Trying to understand how to run 3_job_AdaptiveIndexDefrag.sql in an AzureSQL database is unclear, the only guidance in the scripts is on the usp_AdaptiveIndexDefrag.sql and it just says:

-- If you are using AdaptiveIndexDefrag together with the maintenance plans in http://blogs.msdn.com/b/blogdoezequiel/archive/2012/09/18/about-maintenance-plans-grooming-sql-server.aspx
-- please note that the job that runs AdaptiveIndexDefrag is expecting msdb. As such, change the database context accordingly.

But what is the context? what about the tables that don't exist in AzureSQL? tables and views like dbo.sysjobs don't exist so how are jobs managed and created?

Dominant language
Jupyter Notebook
Stars
1.6k
Forks
749
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/tigertoolbox

All issues in microsoft/tigertoolbox

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.