One of the most important features of the SQL Server 2016's new Query Store is the reporting. With these features, it is now possible to get a wealth of information on how your query workload is performing, either aggregated for the entire query workload or for a single query. With this information, you can see the effects of 'forcing' an execution plan for specific queries and get feedback of the consequences.
2016-01-29
4,359 reads
By Vinay Thakur
As this is an Artificial Intelligence (AI) World, things are changing. We can see that...
In a containerized app, React and Chakra UI provide a robust and accessible user...
By Steve Jones
nachlophobia – n. the fear that your deepest connections with people are ultimately pretty...
Comments posted to this topic are about the item More Funny SELECTs
Comments posted to this topic are about the item Reducing the Cycle Time
I've set up replication in my SQL 2019 environment in attempt to migrate SQL...
What does this code return?
SELECT
( SELECT COUNT (*), MAX(soh.OrderDate) AS latestorder
FROM Sales.SalesOrderHeader AS soh
WHERE
soh.OrderDate > '01/01/2011'
AND soh.OrderDate < '01/01/2012') AS OrdersIn2000
, ( SELECT COUNT (*), MAX(soh.OrderDate) AS latestorder
FROM Sales.SalesOrderHeader AS soh
WHERE
soh.OrderDate > '01/01/2012'
AND soh.OrderDate < '01/01/2013') AS OrdersIn2001
, ( SELECT COUNT (*), MAX(soh.OrderDate) AS latestorder
FROM Sales.SalesOrderHeader AS soh
WHERE
soh.OrderDate > '01/01/2013'
AND soh.OrderDate < '01/01/2014') AS OrdersIn2002;
GO See possible answers