{"id":1403,"date":"2014-03-05T09:00:00","date_gmt":"2014-03-05T17:00:00","guid":{"rendered":""},"modified":"2024-01-22T22:49:01","modified_gmt":"2024-01-23T06:49:01","slug":"top-3-features-im-excited-about-in-sql-server-2014","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2014\/03\/05\/top-3-features-im-excited-about-in-sql-server-2014\/","title":{"rendered":"Top 3 Features I\u2019m Excited About in SQL Server 2014"},"content":{"rendered":"
*\u00a0\u00a0\u00a0\u00a0 *\u00a0\u00a0\u00a0\u00a0 *\u00a0\u00a0\u00a0\u00a0 *\u00a0\u00a0\u00a0\u00a0 *<\/p>\n SQL Server 2014 is almost here! Many SQL Server professionals have been following the progress of this new release for a long time, and others have been so busy with day-to-day fire-fighting they haven\u2019t had a chance to look at what\u2019s coming. As the SQL Server team joins with PASS<\/a> Virtual Chapters on a free \u201cCountdown to SQL Server 2014\u201d webinar series<\/a>, I thought it would be a great time to highlight some of the features I\u2019m most excited about.<\/p>\n Among the host of SQL Server 2014 capabilities that will enable innovative, new application and data platform opportunities, here are three of my favorites I can\u2019t wait for the community to try out:<\/p>\n 1. Delayed Durability<\/b> 2. New Cardinality Estimation Design<\/b> 3.<\/strong> Clustered Columnstore Indexes<\/strong> These are just a few of the SQL Server 2014 features I think will be game-changers in many organizations, helping us deliver even higher performing and more highly scalable data systems. Which features are you most excited about? Let us know how you plan to use them. And I hope you\u2019ll join PASS and Microsoft to learn more about this new release and how to take full advantage of it \u2013 sign up for your favorite webinars today<\/a>.<\/p>\n See you out there! Guest blog post by:\u00a0 SQL Server MVP Adam Jorgensen \u2013 PASS Executive Vice President, Finance & Governance, and President of Pragmatic Works \u2013 has been leading innovative SQL Server and Business Intelligence organizations for over a decade.<\/p>\n","protected":false},"author":1457,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","footnotes":""},"post_tag":[],"product":[],"content-type":[2445],"topic":[],"coauthors":[2487],"class_list":["post-1403","post","type-post","status-publish","format-standard","hentry","content-type-thought-leadership"],"yoast_head":"\n
<\/a>Guest blog post by<\/strong>:\u00a0 SQL Server MVP Adam Jorgensen \u2013 PASS Executive Vice President, Finance & Governance, and President of Pragmatic Works \u2013 has been leading innovative SQL Server and Business Intelligence organizations for over a decade. His passion is finding new and creative avenues for clients and the community to embrace innovation and lower barriers to implementation. You can read his blog at\u00a0AjBigData.com<\/a>\u00a0and follow him on Twitter at\u00a0@AJBigData<\/a>.<\/p>\n
<\/b> SQL Server 2014 lets us mark certain transactions as delayed durable<\/a>, meaning control returns to the client before the log record is written to disk, as opposed to fully durable, which hardens the transaction log to disk before returning control to the client. Also called Lazy Commit, delayed durability can help reduce latency related to log I\/O by keeping the transaction log records in memory and writing to the transaction log in batches.\u00a0 If you\u2019re experiencing log I\/O contention, it can also help reduce waits in the system. This setting \u2013 which we can control at the database, commit, or atomic level \u2013 provides for many new scalability opportunities and challenges. I\u2019m looking forward to the solutions our community will create to leverage this capability.<\/p>\n
<\/b>The cardinality estimator has been redesigned in SQL Server 2014 to improve query plan quality and query performance. This new estimator calculates cardinality, essentially the number of rows the optimizer processes in an operation, using assumptions and algorithms that support modern OLTP and data warehousing workloads.\u00a0The Microsoft SQL Server engineering team did a lot of research on these workloads to deliver a modern algorithm set that is customer tested and proven. You can read more about the new estimator in Books Online: What\u2019s New (Database Engine)<\/a> and in the white paper \u201cTesting cardinality estimation models in SQL Server<\/a>.\u201d<\/p>\n
Since SQL Server 2012 introduced nonclustered columnstore indexes, many of us have been looking forward to clustered columnstore indexes<\/a> and seeing this new SQL Server 2014 feature in action in our own environments. A clustered columnstore index will improve data compression and query performance for many data warehousing workloads, especially in read-heavy and bulk-loading scenarios. And because the CCI is updatable, we can perform Selects, Inserts, Updates, and Deletes on these tables while still getting the performance of a clustered columnstore.<\/p>\n
Adam<\/p>\n","protected":false},"excerpt":{"rendered":"