未加星标

T-SQL Tuesday 86: SQL Server Bugs & Enhancement Requests

字体大小 | |
[数据库(mssql) 所属分类 数据库(mssql) | 发布者 店小二03 | 时间 2017 | 作者 红领巾 ] 0人收藏点击收藏

T-SQL Tuesday 86: SQL Server Bugs & Enhancement Requests
Let’s kick off the new year with a T-SQL Tuesday! This month’s edition is hosted by Brent Ozar:

Announcing T-SQL Tuesday #86: SQL Server Bugs & Enhancement Requests

Brent wants us to blog about our favorite Connect items because Microsoft is currently listening to its customers and actually closing items. So it is the time to take advantage! TheConnect item that I’m going to highlight was submitted by Niko Neugebauer ( blog | twitter ) and is of course about columnstore indexes:

Implement Batch Mode Support for Row Store

One of the biggest advantages of columnstore indexes aside from the huge compression ratio is Batch Mode. With batch mode, certain operators in a query plan work on blocks of 1,000 rows at a time instead of doing operations row by row. This is a huge performance improvement: doing something once to 1,000 rows instead of doing it 1,000 times to an individual row tends to be faster. The downside is that it only works on tables with a columnstore index (clustered or non-clustered). If the table is in row storage, batch mode is not available and that’s what the connect item is about: make batch mode available in all scenarios. This can have some serious performance impact.

With SQL Server 2016, you can have batch mode on row storage table by using a little trick (detailed by Itzik Ben-Gan in SQLMag.com ):

you can create a filtered non-clustered columnstore index on a single column. For example:

CREATENONCLUSTEREDCOLUMNSTOREINDEXix_dummyONdbo.Table1(col1) WHEREcol1 = 0 AND col1 = 1;

Since col1 cannot be 0 and 1 at the same time, the index will have no data at all. So there is no performance overhead (no writes) and the optimizer will use a constant scan in the plan. However, since a columnstore index is involved, any query on Table1 can now run in batch mode. How crazy is that? This means SQL Server can already execute batch mode just fine on tables that are not really using a columnstore index, so there is no reason for not having this connect item fixed.

At the time of writing, the Connect items is over 2 years old but has only 36 votes. Time to change this! Please go to Connect and upvote it!

本文数据库(mssql)相关术语:熊片数据库 mssql数据库 oracle数据库 pubmed数据库 access数据库 万方数据库

主题: SQLSQL Server
分页:12
转载请注明
本文标题:T-SQL Tuesday 86: SQL Server Bugs & Enhancement Requests
本站链接:http://www.codesec.net/view/522897.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 数据库(mssql) | 评论(0) | 阅读(64)