I love Batch Mode and here is the list of the blog posts that I am writing on this topic:
Batch Mode – part 1 (“The Beginning”)
Batch Mode – part 2 (“Batch Mode on Rowstore in Basics”)
Batch Mode – part 3 (“Basic Heuristics and Analysis”)
Batch Mode – part 4 (“Some of the limitations”)
Batch Mode – part 5 (“TPC-H Queries”)
What are the vector processing(SIMD) operators used in SQL 2016. How does SQL optimizer deal with branch-miss, conditional execution, TLB misses and out of order execution when using InMemory Computing? Is there any tool to check this?
Hi Raju,
I would suggest using Intel’s Tune for this purpose.
I believe that Microsoft sees no reason for providing any direct insight on those matters, since they can & are being changed regularly.
Best regards,
Niko Neugebauer
We are using Clustered Column store Indexes in multiple tables. To determine Fragmentation,
When I use sys.dm_db_column_store_row_group_physical_stats I see 0% fragmentation,
When I query sys.dm_db_index_physical_stats I see 90.10% fragmentation also Index properties show Page fullness as 62.5% and Total fragmentation as 90.10%.
Column Store Index Properties
Which fragmentation should be taken as actual fragmentation for my table. And can I remove the fragmentation by rebuild index or rebuild of partitions for column store will work.
Hi Manish,
take a look over there http://www.nikoport.com/2014/07/29/clustered-columnstore-indexes-part-36-maintenance-solutions-for-columnstore/ and here http://www.nikoport.com/2015/06/28/columnstore-indexes-part-57-segment-alignment-maintenance/
http://www.nikoport.com/2014/07/20/clustered-columnstore-indexes-part-34-deleted-segments-elimination/
There is no fiscal fragmentation, just the logical one.
Best regards,
Niko Neugebauer