Its nice, but I need to use Real tables.
Like the ATTACHED SQL. Blowing up the tables.. And then here is the plan below of what time m trying to do. This is a POC demo for a group of DBAs and product owners...
POC PLAN FOR CCI and CCI ON IN-MEMORY TABLES
For live demo
DEMO 1: REGULAR TABLE (NON MEMORY OPTIMIZED)
* Creating a test table () conforming to the rules of table design that qualifies for Memory Optimized table and CCI.
* Populating it with 10+ million rows with random values
(I'll create a script for automating such test data entry load)
Running a HEAVY query against the table
(+ noting/saving/documenting (bad) stats and query plan)
Creating a couple of regular Clustered and Non-clustered indexes
Running same HEAVY query against the table (+ noting/documenting
(improved) run stats and query plan)
Dropping regular Clustered and Non-clustered indexes and creating Vertical Indexes (CCI and CI)
Running the same HEAVY query against the table (+ noting/documenting
(DRASTICALLY improved) stats, speed, and query plan)
DEMO 2: MEMORY OPTIMIZED TABLE: Same steps as in DEMO 1 using the
* Same table recreated as In-Memory and re-populated with test data
before running the above steps 2, 3, and 4.
* Running the same HEAVY query against the table
(+ noting/documenting (REMARKABLY improved) stats, speed, and query plan)
likes to play chess