I added the Profiler module to AZure Data Studio in our ("Microsoft Azure SQL Data Warehouse ) env to monitor performance memory / disk, etc just as I've done with SSMS profiler for years.. I know I 've used it before on another Azure product, but for this I get:
"An exception occurred while executing a Transact-SQL statement or batch. ---> Catalog view 'dm_xe_database_sessions' is not supported in this version."
And it wont run.. it tries to run then errors with the above. Anyone else have this happen,or fix or found a workaround to see the IO/ Memory and duration cost of your queries so I can make performance improvement. ?
- This topic was modified 3 months, 3 weeks ago by digdave7.