Offer a query plan modern approach - AKA avoid "old" set showplan_xml

[IloveFabric]

Something like gorgeous Snowflake & Bigquery query plan graphical VIEVERS

- Explain main steps

- With metrics each time ( rows & volumetry scanned - returned rows & volumetry) 

- Techno used to reduce computing ( cache OR clustering key etc ..)

- Give TSQL advises how to reduce computing

Current SET SHOWPLAN_XML is an example of SQL SERVER "old" techno badly recycled on MS Fabric