`New-FabricSQLDatabase` should provide progress and maybe a `-NoWait` option

[SQLDBAWithABeard]

Problem description

The function creates a Fabric SQL Database. It takes a significant amount of time to return and also the Fabric SQL Database is available in the workspace before the function completes

Suggest a progress return and also maybe a no wait switch

Verbose logs

PS > New-FabricSQLDatabase -WorkspaceId 9e52da3e-8c56-42dd-ad44-d4452114c0b3 -Name test3 -Description yep  -Verbose
VERBOSE: Check if session is established and token not expired.
VERBOSE: Show current session object
VERBOSE: Show current session object
VERBOSE: Performing the operation "Create SQL Database" on target "https://api.fabric.microsoft.com/v1/workspaces/9e52da3e-8c56-42dd-ad44-d4452114c0b3/sqldatabases".
VERBOSE: Requested HTTP/1.1 POST with 55-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
[2025-06-14 11:04:32] [Info] SQL Database 'test3' creation accepted. Provisioning in progress!
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8
VERBOSE: Requested HTTP/1.1 GET with 0-byte payload
VERBOSE: Received HTTP/1.1 response of content type application/json of unknown size
VERBOSE: Content encoding: utf-8

id          : e0052ed9-2f65-431f-8746-ed60121e79cc
type        : SQLDatabase
displayName : test3
description : yep
workspaceId : 9e52da3e-8c56-42dd-ad44-d4452114c0b3

Module Version

pre-release

Suggested solution

add a nowait switch and a progress

[NowinskiK]

@SQLDBAWithABeard I think it's a good idea.
Even though I did not notice such a delay in creation, it may happen often.
I was thinking about all functions by adding -wait switch parameter, but I didn't do enough research to present this as an issue yet.
I saw -wait that is being used in Restore-FabricRecoveryPoint, but I didn't explore it further yet.
However, -nowait can be more useful, because the synchronous (with wait) approach should be default.

Open to discussion (in broader context for potential other functions with LRO):
a) wait = $true (default) OR
b) nowait = $false (default)
The latter is double negative, therefore perhaps wait would be a better fit?

In context of progress - do we have enough information to present something like remaining time?

I'm happy for you to develop this feature in the function.

[SQLDBAWithABeard]

Please notice that the option I am suggesting is -NoWait to match the usual PowerShell uses in commands like Start-AzVM and Stop-Service

[SQLDBAWithABeard]

What is LRO? Acronyms without explanations can lead to misunderstanding.

[NowinskiK]

Sorry, I wrongly assumed you know it: LRO = Long-Running-Operation (LRO) response.
Some Fabric API (not all) supports LRO, which means an async approach should be handled (like in this case):
https://learn.microsoft.com/en-us/rest/api/fabric/sqldatabase/items/create-sql-database?tabs=HTTP

Creates a SQL database in the specified workspace.
This API supports long-running operations (LRO).

The New-FabricSQLDatabase is the first function where I used a unified function to handle errors and LRO if needed - Test-FabricApiResponse

PS. If there is a standard to use -NoWait - it's an easy decision then. Thanks for showing the example.