June 1, 2016 at 8:00 am
yb751 (6/1/2016)
Hugo Kornelis (5/30/2016)
yb751 (5/30/2016)
This is great Hugo!On a side note it might have been worth mentioning that you'll need an enterprise edition of SQL to try it out.
You are right, I should have added that.
By the way, for testing it you can also use Developer Edition. That edition has all the features of Enterprise Edition without the cost (but obviously not licensed for production use). This used to be a bargain at I think 50 bucks or so, and recently Microsoft announced that Developer Edition will be completely free going forward. Not sure if that "completely free" applies to the SQL Server 2016 version only or also to older versions.
I could be wrong but I believe the free developer edition only applies to 2014 & 2016. My local copy for testing is 2012 so that I can mirror my production environment. However, I may consider also installing 2014 just so I can at least test some of the features I currently don't have access to.
That's my understanding too ... 2014 onwards.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
June 8, 2016 at 7:57 pm
Great article Hugo. Very well researched and written. I just started the series and look forward to the rest.
I have neen reading up on columnstore indexes recently and just read 0b]What You Need to Know about the Batch Mode Window Aggregate Operator in SQL Server 2016: Part 1[/b]. Ben-Gan talks about how to trick the optimizer into us I'll ml get Batch mode even when a columnstore index is not present. Very cool stuff.
-- Itzik Ben-Gan 2001
January 7, 2017 at 8:46 am
Great article series. We're now looking into an upgrade to sql 2016 in order to take advantage of column store indexes and in-memory-oltp. Currently we have one main customer database of about 5.5 TB which has a mix of perhaps 75% OLTP and 25% reporting-style queries.
What I'm looking for first is documentation on "gotchas" in either of those technologies for our situation.
Currently on sql 2012 Enterprise.
January 7, 2017 at 9:09 am
Indianrock (1/7/2017)
Great article series. We're now looking into an upgrade to sql 2016 in order to take advantage of column store indexes and in-memory-oltp. Currently we have one main customer database of about 5.5 TB which has a mix of perhaps 75% OLTP and 25% reporting-style queries.What I'm looking for first is documentation on "gotchas" in either of those technologies for our situation.
Currently on sql 2012 Enterprise.
This stairway series was started before SQL 2016 was out, and I made the choice to not shift focus half-way. All levels currently out, as well as level 12 (that I am currently writing on), focus on SQL 2012 and SQL 2014.
Instead of shifting halfway to include SQL 2016, I have chosen to add one extra level (probably going to be level 13), which will cover all changes in SQL Server 2016. However, these changes are very manifold, so I will only be able to scratch the surface in that single level.
A very exhaustive and in-depth coverage of columnstores can be found in the blog series written by Niko Neugebauer, the technical editor for this stairway. See http://www.nikoport.com/columnstore/[/url]. It is an extremely long series. Starting from part 54 the improvements and changes in SQL 2016 are explained. (The 53 levels before that focus mainly on SQL 2014 and generic architecture; they were written before previews of SQL 2016 were available)
December 18, 2019 at 1:11 pm
Excellent and well-written. Unfortunately I'm still on SS 2008! However, that changes in January. So, hopefully I get a chance to practice this technology. Thanx!
Wallace Houston
Sunnyland Farms, Inc.
"We must endeavor to persevere."
October 21, 2021 at 12:56 pm
Appreciate this was posted a while back, I ran the same queries (including the index creation) on SQL server 2019 on my Intel core7 (8 gen) Laptop. The estimated Execution Mode still shows as "Row" !
Can you please help ?
October 21, 2021 at 1:12 pm
Appreciate this was posted a while back, I ran the same queries (including the index creation) on SQL server 2019 on my Intel core7 (8 gen) Laptop. The estimated Execution Mode still shows as "Row" !
Can you please help ?
Can you please do the following for me:
1. Right-click somewhere in the white space of the execution plan area, then choose "Save Execution Plan As...". Provide a filename and path, leave the default extension as .sqlplan, Find the file on your computer (in the specified path) and upload it here as an attachment to your reply.
2. Run the following query, then copy/paste the results in your reply: SELECT SERVERPROPERTY ('Edition');
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply