microsoft / microsoft/sqlmanagementobjects
The space available property is not computed correctly
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
The Database.SpaceAvailable property is not computed correctly. The reason for this issue is that the input used in the calculation of this property, as seen in the source code, relies on a join operation between the sys.allocation_units and sys.partitions DMVs. However, this inner join is incompatible with columnstore indexes, as clearly documented in the official documentation. Consequently, the size is inaccurately computed for databases using columnstores. The solution is straightforward: remove this incompatible join operation from the calculation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/Microsoft/SqlServer/Management/SqlEnum/PostProcessDatabaseInsideAttribs.cs at the linked calculation of Database.SpaceAvailable. Review how sys.allocation_units and sys.partitions are joined, then verify the result for a database using columnstore indexes. Done means the property reports the correct available space without the incompatible join.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100