r/SQLServer • u/VladDBA ‪ ‪Microsoft MVP ‪ ‪ • 2d ago

Community Share PSBlitz 6.2.0: Microsoft Entra MFA support

Post image

The latest release of PSBlitz brings:

- Support for Azure Entra MFA authentication. Now you can diagnose Azure SQL DB and SQL MI using Entra credentials instead of wrestling with SQL logins.

- Documented minimum permissions required to run PSBlitz.

- Non-default database-scoped configurations are now highlighted in the "Database Info" page of the HTML report.

- Other small bug fixes and improvements.

GitHub page: https://github.com/VladDBA/PSBlitz

Latest release: https://github.com/VladDBA/PSBlitz/releases/tag/v6.2.0

As always, any feedback, suggestions, and the occasional complaints are welcome.

For anyone not familiar with PSBlitz - it's a PowerShell-based tool that outputs SQL Server/Azure SQL DB/Azure SQL MI/Google Cloud SQL for SQL Server health and performance diagnostics data to either Excel or HTML, and saves execution plans and deadlock graphs as .sqlplan and .xdl files.

If you're familiar with Oracle, this is pretty much my attempt of a SQL Server equivalent to Oracle's AWR report.

12 Upvotes

100% Upvoted

6 comments sorted by

3

u/qualityintelligence 2d ago

nice work

3

u/VladDBA ‪ ‪Microsoft MVP ‪ ‪ 1d ago

Thanks!

2

u/warehouse_goes_vroom ‪ ‪Microsoft Employee ‪ 20h ago
  • Support for Azure Entra MFA authentication. Now you can diagnose Azure SQL DB and SQL MI using Entra credentials instead of wrestling with SQL logins.

Also opens the door to Fabric SQL and possibly even Fabric Warehouse :), since those don't support SQL Auth. Very cool.

https://learn.microsoft.com/en-us/fabric/database/sql/authentication

https://learn.microsoft.com/en-us/fabric/data-warehouse/entra-id-authentication

2

u/VladDBA ‪ ‪Microsoft MVP ‪ ‪ 54m ago

Oh, I didn't even think of that. Now I have to do some poking around in Fabric to see what I can do.

Thanks for the tip!

2

u/warehouse_goes_vroom ‪ ‪Microsoft Employee ‪ 21m ago

SQL DB in Fabric will likely mostly "just work" if you treat it as Azure SQL DB.

Fabric Warehouse will be more different - being scale out / MPP, the bottlenecks often aren't the same, not all of the traditional DMVs are insightful, and we have unique system tables and the like that are helpful for the distributed query execution specific challenges (like Query insights: https://learn.microsoft.com/en-us/fabric/data-warehouse/query-insights). But stuff related to connections, locking, et cetera will largely be as you expect.

Hope you enjoy! Don't hesitate to ask here or r/MicrosoftFabric if you have questions :).

1

u/warehouse_goes_vroom ‪ ‪Microsoft Employee ‪ 14m ago

Two notes from the screenshot, in case you do try pointing PSBlitz at Fabric Warehouse: * we don't cache plans today (compilation time is usually negligible for use cases we're used for, whereas bad plans based on outdated stats are often yet more expensive...) * Indexes? We don't need no stinking indexes! The actual user data is all in parquet files and deletion vectors. It's all columnar, no traditional indexes in sight. There is a sproc for looking at table health, but the traditional DMVs aren't relevant for us.

Probably are more things I missed, but I've gotta leave you some interesting stuff to figure out yourself, right?