Index-Information - KeyCols_data_length_bytes also aggregates for included columns

Open
#291 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
sql
Domain
database

Research direction

Start with view_IndexInformation.sql at line 678 and view_IndexInformation_CurrentDB.sql at line 698. Inspect the WHERE clause used for KeyCols_data_length_bytes and verify the resulting aggregation excludes included columns while retaining key columns; confirm both views reflect the intended behavior.

Written by the indexing model from the issue text.

Description

Line 678 in view_IndexInformation.sql and line 698 for view_IndexInformation_CurrentDB.sql are aggregating for Key and included columns. Adding "and sic.is_included_column = 0" into the WHERE clause for the "KeyCols_data_length_bytes" column will stop the aggregation from picking up included columns.

Dominant language
Jupyter Notebook
Stars
1.6k
Forks
749
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 Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.