Executing usp_AdaptiveIndexDefrag in a Azure Data Factory (ADF) activity

Open
#270 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, sql
Domain
cloud, databases

Research direction

Start by comparing the Azure Data Factory stored procedure activity with the successful SSMS execution of dbo.usp_AdaptiveIndexDefrag. Inspect the procedure and tbl_AdaptiveIndexDefrag_log, using the SQL Profiler observation as a starting point. Done means identifying why the ADF run completes without maintenance or a log row, and documenting or fixing that behavior.

Written by the indexing model from the issue text.

Description

Hi,

I use Azure Data Factory (ADF) in my project. I would like to extend the use of ADF to do the maintenance of the Azure SQL Database but it doesn't work.

I can execute the stored procedure usp_AdaptiveIndexDefrag in SSMS and it works very well (thanks! 👍 ).
I have my pipeline with the stored procedure activity, but the execution takes only 4 seconds. It ends OK but nothing has been done: there is no row in tbl_AdaptiveIndexDefrag_log for example.
With the SQL Profiler, I see the query "exec [dbo].[usp_AdaptiveIndexDefrag]" but it doesn't help me...

Do you have an idea to fix this?

ADF_index

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.