Skip to content

Added exclusion for backup-related waits to GetLongRunningQueriesAsync() method.#4

Merged
HannahVernon merged 1 commit into
devfrom
feature/add-exclusion-for-BACKUPTHREAD-to-long-running-queries
Feb 27, 2026
Merged

Added exclusion for backup-related waits to GetLongRunningQueriesAsync() method.#4
HannahVernon merged 1 commit into
devfrom
feature/add-exclusion-for-BACKUPTHREAD-to-long-running-queries

Conversation

@HannahVernon
Copy link
Copy Markdown
Owner

What does this PR do?

Adds and exclusion for backup-related waits to the GetLongRunningQueriesAsync() method to avoid unnecessarily reporting backups as long-running. The thought here is of-course-they-are-long-running and as such don't need to be reported. Feel free to decline this if you do not agree, or perhaps make the method parameter false by default instead of true. At some point when I get around to it I intend to add these parameters to the settings dashboard for user-configurability.

Which component(s) does this affect?

  • [✔] Full Dashboard

How was this tested?

Tested against 4 instances of SQL Server 2022 with WSFC Availability Group.

Checklist

  • [✔] I have read the contributing guide
  • [✔] My code builds with zero warnings (dotnet build -c Debug)
  • [✔] I have tested my changes against at least one SQL Server version
  • [✔] I have not introduced any hardcoded credentials or server names

…c() method. Removed System.Collections.Generic using statement as it is unnecessary.
@HannahVernon HannahVernon merged commit 9c2c5f2 into dev Feb 27, 2026
3 checks passed
HannahVernon added a commit that referenced this pull request Mar 27, 2026
…eout

- DuckDbInitializer.AcquireWriteLock() now accepts optional TimeSpan timeout
  to prevent indefinite blocking when archival holds the lock
- DismissAlertsAsync uses exclusive write lock + single batched UPDATE with
  VALUES list + BEGIN/COMMIT/ROLLBACK transaction for all-or-nothing semantics
- DismissAllVisibleAlertsAsync uses exclusive write lock (was read lock)
- OpenWriteConnectionAsync uses 5-second timeout to prevent UI freeze
- UI dismiss handlers catch TimeoutException with friendly retry message
- LockedConnection updated to document both read and write lock usage
- 7 new tests covering batched UPDATE, transaction commit/rollback,
  write lock exclusivity, and timeout behavior (225 total, all passing)

Addresses items #4, #5, erikdarlingdata#11 from issue erikdarlingdata#718 improvement list.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant