Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item_hover". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item_hover_pointer_bg". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Notice: Function Elementor\Controls_Manager::add_control_to_stack was called incorrectly. Cannot redeclare control with same name "color_menu_item_active". Please see Debugging in WordPress for more information. (This message was added in version 1.0.0.) in /home/site/wwwroot/wp-includes/functions.php on line 6121

Understanding Columnstore Indexes in SQL Server Part 2

In my last blog I explained what a columnstore index is, in this blog, we will dive into creating a clustered columnstore index and look at the performance differences the index can make. Let’s get started. Using AdventureworksDW2016CTP3 we will work with the FactResellerSalesXL table which has 11.6 million rows in it. The simple query we will use as a demo just selects the ProductKey and returns some aggregations grouping them by the different product keys. First, we will run the query with no existing columnstore index and only using the current clustered rowstore (normal) index. Note that I turned… Continue reading