See, that’s not a regular execution plan, at all. ( DATE NOT NULL, NVARCHAR(50) COLLATE SQL_Latin1_General_CP1_CI_AS, MONEY NOT NULL ) WITH(DATA_COMPRESSION=PAGE) ( INT NOT NULL, INT NOT NULL, MONEY NOT NULL ) WITH(DATA_COMPRESSION=PAGE) ( INT NOT NULL, DATE NOT NULL ) WITH(DATA_COMPRESSION=PAGE) SELECT dd.FullDateAlternateKey AS OrderDate, dc.LastName, SUM(fis.SalesAmount) AS SumSalesAmount FROM dbo.FactInternetSales AS fis JOIN dbo.DimDate AS dd ON fis.OrderDateKey = dd.DateKey JOIN dbo.DimCustomer AS dc ON dc.CustomerKey = fis.CustomerKey GROUP BY dd.FullDateAlternateKey, dc.LastName HAVING SUM(fis.SalesAmount) > 5000.0 ORDER BY OrderDate DESCĬREATE TABLE. Instead I had to copy and paste the XML into an XML file window that I created within Visual Studio. In my version of Visual Studio (2015), I didn’t find that to be the case. What you get is XML output in the results like this:Īccording to the documentation on EXPLAIN, I should be able to click on the XML and it will open up to explore.

This is how we generate an execution plan from within Azure SQL Data Warehouse. If I run this through the SSMS query window, I get a syntax error. SELECT dd.FullDateAlternateKey AS OrderDate, So… now what? Enter our new command: EXPLAIN Same thing if I try to capture a plan using Visual Studio. If I try to use T-SQL commands, I get an error that those commands are not supported with this version of SQL Server. If I attempt to capture an execution plan using the SQL Server Management Studio GUI, nothing happens. Here’s a query against that database: SELECT dd.FullDateAlternateKey AS OrderDate, I’ve created a new SQL Data Warehouse using the sample database available on the portal, AdventureWorksDW. Azure SQL Data Warehouse can sometimes feel like it’s completely different from SQL Server, but under the covers, it is still (mostly) SQL Server and it does have execution plans.

Execution plan azure data studio