Azure / Azure/azure-powershell
Get-AzSqlServer - Returns SQL Servers which have to be managed by Synapse Cmdlets
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 51
Description
## Description
Get-AzSqlServer returns all SQL Servers, including Managed SQL by Synapse Workspace.
It's not possible to determine by results what kind of resource it's.
Can we filter out or have property returning what kind of SQL Server it's so we know if we should use AzSqlServer to manage it or if it should be managed by AzSynapse as it's Managed SQL by Synapse.
## Steps to reproduce
Get-AzSqlServer
## Environment data
Name Value
---- -----
PSVersion 7.1.3
PSEdition Core
GitCommitId 7.1.3
OS Microsoft Windows 10.0.19041
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
## Module versions
ModuleType Version PreRelease Name PSEdition ExportedCommands
---------- ------- ---------- ---- --------- ----------------
Script 5.6.0 Az Core,Desk
Script 2.16.0 Az.Sql Core,Desk {Get-AzSqlDatabaseTransparentDataEncryption, Get-AzSqlDatabaseTranspar…
Script 0.8.0 Az.Synapse Core,Desk {Get-AzSynapseSparkJob, Stop-AzSynapseSparkJob, Submit-AzSynapseSparkJ…
## Debug output
## Error output
Contributor guide
Research direction
Start with the Get-AzSqlServer entry point and reproduce the behavior using Get-AzSqlServer. Compare the returned SQL Server resources with the Az.Synapse management distinction; the issue is done when Synapse-managed SQL Servers can be filtered out or identified reliably so callers know which cmdlets to use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, powershell, sql
- Domain
- cli, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100