microsoft / microsoft/azure-sql-database-container

[Bug]: Accessing the properties of a database from SSMS returns a "Property SpaceAvailable is not available" error

Open
#134 0 comments 0 reactions 1 assignee View on GitHub

@ericjulien is already working on this.

Since Aug 6, 2026.

bug User-filled
Dominant language
Shell
Stars
17
Forks
4
Avg merge
9h 49m
Merged PRs (30d)
15

Description

Container image tag

sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io/azure-sql/db-dev:latest

Host OS

Windows 11 (x86_64)

Container runtime and version

Podman 5.8.5

What happened

When trying to access the properties of a database created in the container (Object Explorer > right click on the database > click on Properties) the following error message is thrown:

Image

Text version:

TITLE: Microsoft SQL Server Management Studio
------------------------------

Cannot show requested dialog.

------------------------------
ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

------------------------------

Property SpaceAvailable is not available for Database '[azure_sqldb_test2]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)

For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=18.100.11.28&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.PropertyCannotBeRetrievedExceptionText&EvtID=SpaceAvailable&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

The same behavior is replicated on the Azure SQL DB Dev container running on QNAP's (Linux QTS 5.2.10.3568 Build 20260722) Container Station (version 3.1.2.1742), so it's not Windows and/or Podman specific:

Image
Steps to reproduce
  1. Start container (see Podman and QNAP posts for detailed steps on container creation)
  2. Create an empty database with CREATE DATABASE [some_db];
  3. Refresh Object Explorer
  4. Right click on some_db in Object Explorer, click on Properties in the context menu
  5. At this point you should get the error
Additional context

No response

Confirmation
  • I scanned open issues and Known limitations for a duplicate.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.