November 17, 2016 at 7:45 am
Grant Fritchey (11/17/2016)
Ed Wagner (11/17/2016)
I didn't make it through the entire presentation, but I read the announcement - thank you for the link.
Am I reading this right, going completely insane or both? 😉 Does this mean that our on-premise SE will be able to use the EE features like compression, columnstore and hekaton?
What does this mean for the cost of licensing? I ask because I'm stuck on SE all the way around due to licensing costs. If I'm reading this correctly, I've never heard a better argument for upgrading.
Both.
Columnstore and Hekaton and compression, all on SE. No added costs. There are some things that are still EE only like some of the encryption options. Also the limits on memory & CPU are still in place. The idea is that core functionality should just work across the stack. It's pretty amazing.
Absolutley. Driving force for upgrades will change from "need a feature that is Enterprise Edition only" to "need scale / performance that only Enterprise Ediition offers". Which, in my opinion, is a far easier proposition to explain to management.
EDIT: To clarify, *some* features that were enterprise only were in my opinion also easy to explain and understand. But not all. Stuff like compression and TDE should, in my opinion, have been in all editions from the time they were released, and I am glad that this is now finally the case. I'll take the extra features as a bonus
November 17, 2016 at 7:47 am
Eirikur Eiriksson (11/17/2016)
Brandie Tarvin (11/17/2016)
Beatrix Kiddo (11/17/2016)
It's in the link there.CREATE OR ALTER (Yes, we heard you !!!) – New CREATE OR ALTER support makes it easier to modify and deploy objects like Stored Procedures, Triggers, User–Defined Functions, and Views. This was one of the highly requested features by developers and SQL Community.
I know it's in the link. But none of that tells me anything.
What is CREATE OR ALTER?
That would be CREATE (if not exists) OR ALTER (if exists), bye bye to all the variations of checking if the object exists, create dummy and alter etc.
😎
And best of all, never again risk losing assigned permissions because I accidentally used DROP / CREATE instead of ALTER for an existing object.
Now I only need to get my client to upgrade a few versions.....
November 17, 2016 at 7:51 am
Hugo Kornelis (11/17/2016)
Eirikur Eiriksson (11/17/2016)
Brandie Tarvin (11/17/2016)
Beatrix Kiddo (11/17/2016)
It's in the link there.CREATE OR ALTER (Yes, we heard you !!!) – New CREATE OR ALTER support makes it easier to modify and deploy objects like Stored Procedures, Triggers, User–Defined Functions, and Views. This was one of the highly requested features by developers and SQL Community.
I know it's in the link. But none of that tells me anything.
What is CREATE OR ALTER?
That would be CREATE (if not exists) OR ALTER (if exists), bye bye to all the variations of checking if the object exists, create dummy and alter etc.
😎
And best of all, never again risk losing assigned permissions because I accidentally used DROP / CREATE instead of ALTER for an existing object.
Now I only need to get my client to upgrade a few versions.....
I hope that by "few versions" you don't mean 5 versions. 😀
November 17, 2016 at 7:54 am
Luis Cazares (11/17/2016)
Hugo Kornelis (11/17/2016)
Eirikur Eiriksson (11/17/2016)
Brandie Tarvin (11/17/2016)
Beatrix Kiddo (11/17/2016)
It's in the link there.CREATE OR ALTER (Yes, we heard you !!!) – New CREATE OR ALTER support makes it easier to modify and deploy objects like Stored Procedures, Triggers, User–Defined Functions, and Views. This was one of the highly requested features by developers and SQL Community.
I know it's in the link. But none of that tells me anything.
What is CREATE OR ALTER?
That would be CREATE (if not exists) OR ALTER (if exists), bye bye to all the variations of checking if the object exists, create dummy and alter etc.
😎
And best of all, never again risk losing assigned permissions because I accidentally used DROP / CREATE instead of ALTER for an existing object.
Now I only need to get my client to upgrade a few versions.....
I hope that by "few versions" you don't mean 5 versions. 😀
Let's see... 7 -> 2000 -> 2005 -> 2008/R2 -> 2012 -> 2014 -> 2016. Heh.
Thomas Rushton
blog: https://thelonedba.wordpress.com
November 17, 2016 at 8:28 am
Luis Cazares (11/17/2016)
Hugo Kornelis (11/17/2016)
Eirikur Eiriksson (11/17/2016)
Brandie Tarvin (11/17/2016)
Beatrix Kiddo (11/17/2016)
It's in the link there.CREATE OR ALTER (Yes, we heard you !!!) – New CREATE OR ALTER support makes it easier to modify and deploy objects like Stored Procedures, Triggers, User–Defined Functions, and Views. This was one of the highly requested features by developers and SQL Community.
I know it's in the link. But none of that tells me anything.
What is CREATE OR ALTER?
That would be CREATE (if not exists) OR ALTER (if exists), bye bye to all the variations of checking if the object exists, create dummy and alter etc.
😎
And best of all, never again risk losing assigned permissions because I accidentally used DROP / CREATE instead of ALTER for an existing object.
Now I only need to get my client to upgrade a few versions.....
I hope that by "few versions" you don't mean 5 versions. 😀
Lemme check....
2005 ---> 2008 (1)
2008 ---> 2008R2 (2)
2008R2 --> 2012 (3)
2012 --> 2014 (4)
2014 --> 2016 (5)
*cough* Unless I cheat by ignoring all R2 versions, I'm afraid that I actually do mean 5 versions.
November 17, 2016 at 9:37 am
Hugo Kornelis (11/17/2016)
EDIT: To clarify, *some* features that were enterprise only were in my opinion also easy to explain and understand. But not all. Stuff like compression and TDE should, in my opinion, have been in all editions from the time they were released, and I am glad that this is now finally the case. I'll take the extra features as a bonus
No, unfortunately TDE still is only in Enterprise, unless the feature set has been changed since I looked earlier this morning...
(/grumble rasm' frasm' still have to fork over for EE licenses even in QA...)
November 17, 2016 at 9:50 am
jasona.work (11/17/2016)
Hugo Kornelis (11/17/2016)
EDIT: To clarify, *some* features that were enterprise only were in my opinion also easy to explain and understand. But not all. Stuff like compression and TDE should, in my opinion, have been in all editions from the time they were released, and I am glad that this is now finally the case. I'll take the extra features as a bonusNo, unfortunately TDE still is only in Enterprise, unless the feature set has been changed since I looked earlier this morning...
(/grumble rasm' frasm' still have to fork over for EE licenses even in QA...)
What do you do in QA that means you cannot use a Dev licence?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 17, 2016 at 10:06 am
Ed Wagner (11/17/2016)
Does this mean that our on-premise SE will be able to use the EE features like compression, columnstore and hekaton?
Yes. (once you apply SQL 2016 SP1)
What does this mean for the cost of licensing?
Nothing. Licensing costs are as they were before.
The non-Enterprise editions are still limited on resources, scalability, are missing some features like round robin scans, online index builds, read only replicas, etc. It's the programing surface area that's now the same across all editions.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 17, 2016 at 10:07 am
jasona.work (11/17/2016)
So really, if you could figure out a way to live without Agent, you could drop down to Express and *really* save some money...
And with only 4 cores, 1 GB of memory and max 10GB database size.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 17, 2016 at 10:15 am
GilaMonster (11/17/2016)
jasona.work (11/17/2016)
So really, if you could figure out a way to live without Agent, you could drop down to Express and *really* save some money...And with only 4 cores, 1 GB of memory and max 10GB database size.
Which could be enough for many small (probably medium) companies.
November 17, 2016 at 10:42 am
Luis Cazares (11/17/2016)
GilaMonster (11/17/2016)
jasona.work (11/17/2016)
So really, if you could figure out a way to live without Agent, you could drop down to Express and *really* save some money...And with only 4 cores, 1 GB of memory and max 10GB database size.
Which could be enough for many small (probably medium) companies.
I would doubt it. 10GB is small, and that 1GB memory limit hurts.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 17, 2016 at 10:53 am
Phil Parkin (11/17/2016)
jasona.work (11/17/2016)
Hugo Kornelis (11/17/2016)
EDIT: To clarify, *some* features that were enterprise only were in my opinion also easy to explain and understand. But not all. Stuff like compression and TDE should, in my opinion, have been in all editions from the time they were released, and I am glad that this is now finally the case. I'll take the extra features as a bonusNo, unfortunately TDE still is only in Enterprise, unless the feature set has been changed since I looked earlier this morning...
(/grumble rasm' frasm' still have to fork over for EE licenses even in QA...)
What do you do in QA that means you cannot use a Dev licence?
Well, if I'm finding accurate information, because we refresh our QA from production with real production data, it would be outside the license. And we're real, real, big on staying compliant with licenses here.
I know I need to verify with MS Licensing to be sure, that'll be something for after the holidays (we've already budgeted and paid for EE for our QAs for this fiscal, might as well use it.)
November 17, 2016 at 10:56 am
GilaMonster (11/17/2016)
Luis Cazares (11/17/2016)
GilaMonster (11/17/2016)
jasona.work (11/17/2016)
So really, if you could figure out a way to live without Agent, you could drop down to Express and *really* save some money...And with only 4 cores, 1 GB of memory and max 10GB database size.
Which could be enough for many small (probably medium) companies.
I would doubt it. 10GB is small, and that 1GB memory limit hurts.
It's amazing what some companies will put up with when it's free :Whistling:
November 17, 2016 at 10:56 am
GilaMonster (11/17/2016)
Luis Cazares (11/17/2016)
GilaMonster (11/17/2016)
jasona.work (11/17/2016)
So really, if you could figure out a way to live without Agent, you could drop down to Express and *really* save some money...And with only 4 cores, 1 GB of memory and max 10GB database size.
Which could be enough for many small (probably medium) companies.
I would doubt it. 10GB is small, and that 1GB memory limit hurts.
True story on that.
Previous employer decided Express would be fine for a electronic health records system they were developing, rather than Standard. 3 months after I left customers started hitting the 10GB database size limit, the company had to eat the cost of buying Standard for those customers...
You could probably use it for a small business, but you'd have to be careful what you used it for (inventory system for a small bookseller? Might be OK, but not for a point-of-sale system, I wouldn't think.)
November 17, 2016 at 10:59 am
jasona.work (11/17/2016)
Phil Parkin (11/17/2016)
jasona.work (11/17/2016)
Hugo Kornelis (11/17/2016)
EDIT: To clarify, *some* features that were enterprise only were in my opinion also easy to explain and understand. But not all. Stuff like compression and TDE should, in my opinion, have been in all editions from the time they were released, and I am glad that this is now finally the case. I'll take the extra features as a bonusNo, unfortunately TDE still is only in Enterprise, unless the feature set has been changed since I looked earlier this morning...
(/grumble rasm' frasm' still have to fork over for EE licenses even in QA...)
What do you do in QA that means you cannot use a Dev licence?
Well, if I'm finding accurate information, because we refresh our QA from production with real production data, it would be outside the license. And we're real, real, big on staying compliant with licenses here.
I know I need to verify with MS Licensing to be sure, that'll be something for after the holidays (we've already budgeted and paid for EE for our QAs for this fiscal, might as well use it.)
As far as I know, the fact that you've got prod data in there is not a deal breaker, as long as you are using the environment purely for design, development, test and demonstration purposes. But I understand why you'd be cautious; it's a thin line, sometimes.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 15 posts - 56,656 through 56,670 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply