I already wrote about query performance analysis in lakehouses, but one secret was left behind: The capability to track the queries back to a semantic model, report and visual in a report, identifying the query lineage.
If you check the text of the queries, at the end of the text you will find content like this:
OPTION (label = N”{“DatasetId”:”1269551b-bf26-47de-b0f0-974fa60f7b08″,”Sources”:[{“ReportId”:”01ab9208-399a-47ec-b444-d03633fc3e1d”,”VisualId”:”30ac676503a0bd357312″,”Operation”:”AutoPageRefresh”}]}”)
This has an interesting meaning:
We can use this information to track the query lineage Applications can send lineage (or more) to SQL using OPTION (LABEL) statement Applications Tracking Lineage
If you develop applications