Trace Controller choice causes "This operation is not supported in this version of SQL Server"
- Dominant language
- TSQL
- Stars
- 69
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
When referencing an VM hosted instance of SQL Server running in Azure (SQL Server 2016), it defaulted to the AzureTraceController instead of SqlTraceController.
This causes the "This operation is not supported in this version of SQL Server" error since it tries to create an event session at the database scope rather than server scope. Also the dmv references are incorrect.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the controller is selected for an Azure-hosted SQL Server 2016 VM, then inspect the event-session scope and DMV references used by AzureTraceController and SqlTraceController. Done means the VM uses the appropriate controller without the unsupported-operation error and the DMV references work correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, sql
- Domain
- cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100