Current overview of bugs

[andreasjordan]

I would like to have an overview of all currently open issues with the lable "bugs life" that don't already have a related open pull request.

I would like to have a very short summary of every issue to get an idea of the work needed to solve the issue.

I would like to have the issues grouped by topic so that we can solve similar issues together.

[claude]

Claude finished @andreasjordan's task in 2m 45s —— View job

---

Bug Overview

Tasks

• Understand the request
• Parse provided issue and PR data
• Cross-reference issues against open PRs
• Group and summarize issues by topic
• Post results

---

Issues already covered by an open PR (excluded)

Issue	PR
#10151 DAC behaviour in Connect-DbaInstance on localhost	#10199
#10138 MSX jobs excluded from Get-DbaAgentJob	#10198
#10127 Test-DbaBackupInformation IsVerified property	#10200
#10183 Install-DbaMaintenanceSolution: wrong defaults	#10184 (tests only — fix still needed)

---

Open bugs without a related PR, grouped by topic

---

Connection & Authentication (6 issues)

• (can not reproduce) #10134 Get-DbaDbTable ignores -SqlCredential — Regression in v2.7.23; when running as SYSTEM, the command ignores the SqlCredential and authenticates as the computer account instead. Worked in 2.5.5.

• (functionality should be removed) #9865 Connect-DbaInstance fails with PSCredential for Windows auth — Using domain credentials in a PSCredential works for WMI/CIM calls (Get-DbaDiskSpace) but fails for Connect-DbaInstance with "username or password is incorrect".

• (pr is open) #9750 Get-DbaReportingService doesn't pass -Credential to Get-DbaCmObject — When querying SSRS remotely with a credential, Get-DbaCmObject calls inside Get-DbaReportingService are made without the credential, causing "No version Namespace" error.

• (waiting for OP feedback) #9612 Az SQL DB: redundant Connect-DbaInstance in many functions destroys token-based connections — Piping a token-authenticated connection to functions like Get-DbaPermission triggers a second Connect-DbaInstance that doesn't support Azure auth, destroying the session.

• (can not reproduce) #9084 Export-DbaUser fails on Azure SQL DB — Null reference exception when piping Get-DbaDatabase output to Export-DbaUser against an Azure SQL Database using an access token.

• (closed as solved) #9079 New-DbaAzAccessToken with Managed Identity fails in Azure Function App — "Access denied to socket" error when calling New-DbaAzAccessToken -Type ManagedIdentity from an Azure Function; workaround is Get-AzAccessToken instead.

---

SSIS (4 issues)

• #9876 Copy-DbaSsisCatalog: assembly loading error — Cannot connect to source SSIS; missing Microsoft.SqlServer.Diagnostics.STrace DLL, related to a known older issue ([Bug] Copy-DbaSsisCatalog - Could not load file or assembly Microsoft.SqlServer.IntegrationServices.Common.ObjectModel, Version=15 #6136).

• #9030 Copy-DbaSsisCatalog: can't connect to SSIS services — "ConnectionString property has not been initialized" error; fails to connect to both source and destination SSIS service.

• #8994 Copy-DbaSsisCatalog: IntegrationServices constructor requires zero arguments — New-Object Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices $dest fails because the class has no single-argument constructor.

• #9199 Copy-DbaSsisCatalog: Invoke-ProjectDeployment fails with enumeration error — After creating the folder successfully, project deployment fails with "Unable to match identifier name to a valid enumerator name"; appears to be a parameter type mismatch.

• #9063 New-DbaSsisCatalog fails on SQL Server 2022 — "Method not found: SqlStoreConnection..ctor(System.Data.SqlClient.SqlConnection)" — the constructor signature changed in SQL 2022.

(Note: that's 5 SSIS issues)

---

SQL Agent Jobs & Alerts (4 issues)

• #9853 Copy-DbaAgentJob fails from database mirroring principal — "Use of key 'Failover Partner' requires 'Initial Catalog'" error; Get-DbaAgentJob doesn't handle mirrored connection strings.

• #9316 Copy-DbaAgentJob/Server with -Force loses alert-to-job links — Dropping and recreating a job unlinks any alerts that reference that job; the link is not restored because it belongs to the alert object, not the job.

• #9080 Copy-DbaAgentAlert skips alerts with linked jobs — When an alert is linked to a job, the copy is skipped with "already defined to use…" even with -Force, due to incorrect existence check logic.

• #9336 New-DbaDbMailProfile only allows one mail account — Running the command twice (to add a second account) throws a unique key violation; the function doesn't check if the profile already exists before trying to create it again.

---

Maintenance Solution (1 issue)

• #9051 Install-DbaMaintenanceSolution: AutoScheduleJobs creates wrong schedules — Specifying HourlyLog creates a daily (not hourly) schedule for the LOG backup job; also, omitting a Full/Weekly option causes a null SqlInstance error in New-DbaAgentSchedule.

(#10183 has a test-only PR; the fix for default Verify/Checksum/Compress behavior is still needed.)

---

Availability Groups (4 issues)

• #9220 Export-DbaScript fails for Distributed AGs — SMO scripting throws "Unexpected value for enumeration type AvailabilityGroupAutomatedBackupPreference" for Distributed AGs; regular AGs work fine.

• #9182 Get-DbaAgReplica returns "Unknown" role when querying secondary — The Role property shows Unknown instead of Secondary when the secondary node is passed as SqlInstance.

• #9782 Enable-DbaAgHadr/Set-DbaNetworkConfiguration: Get-RunspaceData WinRM errors — On machines without WinRM configured, service restart triggers CimException errors; the operations actually succeed but errors are misleading.

• #9789 Get-DbaDbOrphanUser: false positives in contained AG — System logins ##MS_PolicyEventProcessingLogin## and ##MS_PolicyTsqlExecutionLogin## are incorrectly reported as orphan users in contained AG system databases.

---

Replication (3 issues)

• #10077 Get-DbaReplSubscription misses some pull subscriptions — For certain subscribers, data exists in the distributor but not in dbo.syssubscriptions; the command queries syssubscriptions only and misses those subscribers.

• #9028 Test-DbaReplLatency broken — Properties like PublicationName and Database cannot be assigned, causing cascading null/empty errors; needs to be rewritten using the new connection pattern from Get-DbaReplServer.

• #9586 Sync-DbaAvailabilityGroup doesn't sync Azure Entra logins — Entra (external provider) logins are not synced to AG secondaries; requires CREATE LOGIN … FROM EXTERNAL PROVIDER syntax.

---

Backup & Restore (4 issues)

• #9303 Invoke-DbaDbLogShipping: fails on first run due to share path timing — Backup fails with "cannot check if path exists" and then null Path on first run; the share path is created but not yet visible to SQL Server; works on second run.

• #9135 Backup-DbaDatabase: duplicate database name in path when using token — When the -Path already contains the dbname token, the database name is also appended at the end by -CreateFolder, resulting in a doubled path.

• #8840 Backup-DbaDatabase: DataReader error on Azure SQL MI — After one successful backup to Azure Blob, all subsequent backup attempts fail with "There is already an open DataReader associated with this Connection."

• #8205 Get-DbaBackupInformation vs Get-DbaDbBackupHistory: inconsistent output — Multiple properties differ: InstanceName always empty, CompressionRatio always 0, Type uses different format, BackupSetId uses different ID field, LastRecoveryForkGUID always zeros, FileList has different property names.

---

Failover Cluster Instances (4 issues)

• (pr is open) #9465 Get-DbaStartupParameter: erratic results against FCI — Returns null objects, arrays of varying length, or empty parameter values when querying FCI virtual network names; works reliably for standalone instances.

• (closed because test was already changed) #10078 Get-DbaPfDataCollectorSet: wrong ComputerName from FCI — Returns the physical node name ($env:COMPUTERNAME) instead of the FCI virtual name; may be expected behavior but the test needs a decision.

• (pr is open) #10080 Test-DbaKerberos: CNAME detection always returns "A" — Uses nslookup output which doesn't include "canonical name" for CNAMEs in English Windows; should use Resolve-DnsName instead. Also, $server.ComputerName always resolves to the A record, so CNAME testing may be structurally limited.

• (can not reproduce) #9315 Test-DbaSpn: returns nothing when one instance lacks TCP/IP — When a machine has multiple SQL instances and one has TCP/IP disabled, Test-DbaSpn returns no results at all instead of results for the TCP-enabled instance.

---

Copy / Migration (3 issues)

• #9039 Copy-DbaPolicyManagement: skips ObjectSets — Policies that reference ObjectSets fail to copy because ObjectSets are not migrated before policies; a proposed fix with ObjectSet migration code is included in the issue.

• (closed as fixed) #9480 Copy-DbaLinkedServer: DAC connection error — Get-DecryptedObject tries to establish a local DAC connection that is refused; occurs even with -WhatIf when source is SQL 2012.

• #9286 Copy-DbaDbTableData: fails with Geography/spatial columns — "'Microsoft.SqlServer.Types.SqlGeography' is an invalid user defined type, reason: no UDT attribute" when bulk copying tables containing spatial data.

---

Extended Events (2 issues)

• #10085 Read-DbaXEFile: database_name column always empty — When reading XEL files, the database_name field is not populated even though the data is present; sys.fn_xe_file_target_read_file returns the value correctly.

• #8726 Export-DbaXECsv: missing events — Exported CSV is missing ~26 rows compared to SSMS export; all output files are ~25MB suggesting a possible internal size limit.

---

Data Masking (2 issues)

• #7941 Invoke-DbaDbDataMasking: temporary MaskingID column not cleaned up — A MaskingID column added to tables without a primary key is never dropped after masking; the column is also created during -WhatIf runs (which should make no changes).

• #7503 Invoke-DbaDbDataMasking: Persisted property ignored for multiple columns — When a masking config has two or more columns with Persisted: true, the property is ignored and each row gets a unique value instead of reusing values deterministically.

---

Other (4 issues)

• #9134 Update-DbaInstance: CredSSP fails in workgroup environment — CredSSP works for normal PSSession but Update-DbaInstance still fails with "username or password is incorrect" even after disabling auto-CredSSP configuration in dbatools.

• (pr is open) #8671 Get-DbaUserPermission: shows wrong Schema — STIG-related schema shows incorrect schema name in output; output logic bug.

• (asked for decision) #8537 Set-DbaDbCompression: always compresses all Views when -Table is specified — The code iterates all Views in the database regardless of the -Table filter, compressing indexed views that were not requested.

• (pr is open) #8874 Export-DbaInstance: missing documentation for required permissions — Multiple sub-commands silently fail when the user lacks sysadmin; the top-level -EnableException doesn't propagate. Requesting better documentation of minimum required permissions.

---

Total open bugs without a related PR: 42 (plus #10183 which has a test-only PR but still needs a fix)

[andreasjordan]

@potatoqualitee @niphlod For me this is very useful. I like to have an overview of all the open topics that we have. Maybe we can build this once a month or every quarter.

We can use this as a base to discuss multiple open issues like "Who uses SSIS and can work on those issues?"

[niphlod]

there are ~170 issues. I guess ~40 "ready to be worked on" is a good guess but, e.g., IMHO some are more "important" than others, and I don't feel this analysis can extract that (even trying to do the same without claude would result in a bit of a pickle, since "the community" isn't really weighin in to discern what's important and what isn't ).
IMHO the stale bot worked wonders in this regard, keeping everyone interested on its toes and closing issues nobody comments on.

But if you're looking for "things to do no matter what", yah, it's as useful as picking one from the opened list at random.