Sample performance with Operational Analytics in WideWorldImporters

This script shows the performance of analytics queries in the operational database. It relies on the Order Insert workload driver.

The main purpose is to show the performance benefits of using nonclustered columnstore indexes for analytics queries on operational systems, and how they limit the impact on the operational workload.

About this sample
Before you begin
Running the sample
Sample details
Disclaimers
Related links

About this sample

Applies to: SQL Server 2016 (or higher), Azure SQL Database
Key features: nonclustered columnstore index
Workload: Operational Analytics
Programming Language: T-SQL
Authors: Greg Low, Jos de Bruijn
Update history: 26 May 2016 - initial revision

Before you begin

To run this sample, you need the following prerequisites.

Software prerequisites:

SQL Server 2016 (or higher) or Azure SQL Database.
SQL Server Management Studio
The WideWorldImporters database (Full version).

Running the sample

Run the Order Insert workload for a while. When starting from the vanilla WideWorldImporters database the recommendation is to run at least 20 minutes, to ensure that enough data is generated and that compression kicks in (the sample has a COMPRESSION_DELAY of 10 minutes for the columnstore indexes).
Execute the sample script.
Open the Messages pane in SSMS and observe the time taken to run the query with and without columnstore index.

Sample details

The Order Insert workload driver is used to simulate an order processing workload. The queries in the sample script are reporting queries run with and without columnstore index.

Disclaimers

The code included in this sample is not intended to be used for production purposes.

For more information, see these articles:

README.md