Open CheetahChrome opened 2 years ago
@CheetahChrome the SQL Profiler installed with SSMS uses the older TRACE technology, whereas ADS Profiler uses XEvents. It's possible that permissions can be configured to allow one or other independently. Can you confirm whether the "XEvent Profiler" available in the SSMS Object Explorer tree works for you, since that should require the same permissions as the ADS Profiler. Thanks!
Yes, with Standard
and TSQL
I have encountered this same issue and have also confirmed the XEvent Profiler is accessible for Standard
& TSQL
, any news here?
Steps to Reproduce:
Connections
-Servers
Select Server to profile and get the green dot.Launch Profiler
Toast message comes up stating
Go to OS and run SQL Profiler and profile the same Server. It works.
Message in Render.Log
Other logs don't have any relevant information.
Does this issue occur when all extensions are disabled?: Yes/No N/A
N/A