November 17, 2016 at 11:03 am
Hugo Kornelis (11/17/2016)
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.
Why in heavens name would you need 2008R2? We skipped from 2008 to 2012 without a problem.
So only 4 versions, really. @=)
November 17, 2016 at 11:12 am
Hugo Kornelis (11/17/2016)
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
Well, this threw my whole day out of control. I've created a PowerPoint and scheduled a room for tomorrow. We've wanted to use some of the EE features for a while now, but because we aren't big enough, we don't spend the money on it. Now that they're included in SE, the only thing I have to sell is upgrading to SQL 2016. Thank you again for the link.
November 17, 2016 at 11:18 am
Ed Wagner (11/17/2016)
Hugo Kornelis (11/17/2016)
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
Well, this threw my whole day out of control. I've created a PowerPoint and scheduled a room for tomorrow. We've wanted to use some of the EE features for a while now, but because we aren't big enough, we don't spend the money on it. Now that they're included in SE, the only thing I have to sell is upgrading to SQL 2016. Thank you again for the link.
See what you do is, go into the room, start the Powerpoint and open with something like "Thank you all for coming here today. We were going to discuss why we should be looking to migrate to SQL Server Enterprise Edition, along with some of the benefits and what it would cost. However (close out of the Powerpoint,) instead we're going to talk about why we should instead migrate to SQL Server 2016 SP1 Standard Edition and how we *won't* need to spend the money on Enterprise Edition, thus saving us from needing to spend several tens-of-thousands of dollars per server for Enterprise."
Then explain what MS did with SP1 and bask in the adulation of the bean-counters.
😎
November 17, 2016 at 11:26 am
jasona.work (11/17/2016)
Ed Wagner (11/17/2016)
Hugo Kornelis (11/17/2016)
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
Well, this threw my whole day out of control. I've created a PowerPoint and scheduled a room for tomorrow. We've wanted to use some of the EE features for a while now, but because we aren't big enough, we don't spend the money on it. Now that they're included in SE, the only thing I have to sell is upgrading to SQL 2016. Thank you again for the link.
See what you do is, go into the room, start the Powerpoint and open with something like "Thank you all for coming here today. We were going to discuss why we should be looking to migrate to SQL Server Enterprise Edition, along with some of the benefits and what it would cost. However (close out of the Powerpoint,) instead we're going to talk about why we should instead migrate to SQL Server 2016 SP1 Standard Edition and how we *won't* need to spend the money on Enterprise Edition, thus saving us from needing to spend several tens-of-thousands of dollars per server for Enterprise."
Then explain what MS did with SP1 and bask in the adulation of the bean-counters.
😎
You know, Jason, the bait-and-switch just might work here. I'll have to add something to my presentation. 😉
November 17, 2016 at 12:52 pm
Just installed MS SQL on a Guest VM (Linux).
This is nuts...I can't help but smile how cool this is. Not quite ready for primetime as certain key services are missing such as SQL Server Agent but it works great nonetheless.
EDIT: FYI - Everything you need to get going is right here: https://docs.microsoft.com/en-us/sql/linux/
November 17, 2016 at 3:33 pm
BWFC (11/16/2016)
Sean Lange (11/15/2016)
Ed Wagner (11/15/2016)
Y.B. (11/15/2016)
Hey Brandie, cheddar is not better!! LOL (it's all personal preference of course)That being said I did recently try an Irish Cheddar which was excellent. I like something with a stronger flavor profile when it comes to cheeses...Asiago, Swiss, Oka. Although I did stray a little too far once and bought some Stinton. Ooooh boy that was something else...acquired taste for sure. Well for me anyway.
Like so many things, it depends on how you're going to use it. For example, a sharp cheddar would never be substituted for gruyere on French onion soup, but I don't know anyone who would use gruyere in a grilled cheese (croque monsieur or croque madame).
If you like strong cheeses (and I do) try a Gorgonzola. It's a type of blue cheese.
--Warning Food discussion starting--
One of my favorite ways to enjoy gorgonzola is to add it to a sauce pan with about the same amount of heavy cream. Then season with a bit of aunt and uncle (salt and pepper). Reduce to about half the volume. Then pour it over a soft polenta mixed with some fresh oregano. Talk about spectacular.
I love cheese, in fact my wife reckons that my sisters and I have a second stomach that no matter how much we've eaten already, we'll find room for cheese and biscuits. Fortunately for my waistline though, said wife is not good with dairy products so we rarely have cheese in the house. I wouldn't trust myself to buy a pound of good cheddar and not scoff the lot on my own in a couple of
dayshours.However, there's steak on the menu for Saturday night and I think I could be tempted to try Ed's sauce...
I reckon that sauce goes better with king-prawns than with steak. Perhaps it might be improved by adding some sliced garlic and a couple of guindillas (with the right meaning of guindilla - it's got different meanings in different places).
Tom
November 17, 2016 at 4:29 pm
He didn't like the answers he got on his original thread, so he started another thread. I pointed out repeatedly that he already had the answer he was seeking on his other thread with a minor modification, but he insisted that this question was different. I finally cut and pasted the answer from the other thread and he marked it as solving the issue.
:crazy:
http://www.sqlservercentral.com/Forums/Topic1834155-3412-1.aspx
Drew
J. Drew Allen
Business Intelligence Analyst
Philadelphia, PA
November 17, 2016 at 5:41 pm
GilaMonster (11/16/2016)
Lynn Pettis (11/16/2016)
Question, any way to get these keynotes to view later? I would like to share these with others here at work. Plus, I came in late.
Actually no, that doesnt work. It gives us the current stuff, it doesn't give us what was sent out about a day ago.
Tom
November 17, 2016 at 6:17 pm
Sean Lange (11/16/2016)
Brandie Tarvin (11/16/2016)
So I did a quick google on polenta and found this interesting article.That's interesting. I have never heard most of those "rules" about polenta.
I looked at it, and found it interesting because I'm used to making porridge with oatmeal rather than cornmeal. But the "real" rules seem to be pretty much the same: soak for a few hours in advance to get coking sooner; stirr enough to prevent binding to th epan bottom, no more; if you haven't soaked your grain in advance (whether corn or oat) don't start with boiling water unless you are going to be watching over it carefully ealy on; don't trust anything that tells you more than 20% grain by volume, and don't even go to 20% if you start with very hot water and haen't done advance soaking; if you see a skin forming, beat it out (and follow the rules more carefully next time). So do the mythical rules, like the rule that you must waste your time stirring continuously.
But polenta (or cooked porridge generally) doesn't appeal to me much; I prefer dramach - oatmeal with water, soaked cold for a long time, no hot cooking; with broilleagan or bananas or blackcurrants or blackberries mixed into it if I want it a bit sweeter, and on occasion a drop of decent whiskey - and/or a bit of salt and a bit more of pepper - mixed in to add flavour).
Tom
November 17, 2016 at 6:30 pm
Hugo Kornelis (11/17/2016)
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
The regrettable thing there is that there's still inadequate encryption in SE - that's not a memory or CPU limit, it's not a "need scale/performance" thing, but still only EE offers it so the basic SE package and still not going to provide adequate security to the average company, only to rich ones, because MS is pretending that something as fundametal as security counts as "needs scale orperformace". Of course on certain interpretations of the word "performance" that's valid, but surely even MS is not so arrogant as to think it wouldn't collect a lot of terrible publicity by pretending it expects peope to interpret the word that way?
Tom
November 17, 2016 at 6:39 pm
Luis Cazares (11/17/2016)
Hugo Kornelis (11/17/2016)
Eirikur Eiriksson (11/17/2016)
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. 😀
So it's OK if he means 6 versions? Or even 7? or all the way forward from SQL SERVER 6.5? :hehe:
Tom
November 17, 2016 at 6:56 pm
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.
Maybe not medium, but if I can raise the energy the definitely small (not medium) CP of which I'm secretary (in the Spanish sense, so responsible for budgets and accounts) will be using EE when I've found time to write the software to replace the really ancient junk currently used that requires too much effort from our full time expert administrator (not a sysadmin! An accounts/projects/purchasing manager/personel manager guy who has to use crap IT because it isn't getting fixed) and causes (because it can't do what's needed) a lot of conflict between the owners.
Tom
November 18, 2016 at 12:42 am
TomThomson (11/17/2016)
GilaMonster (11/16/2016)
Lynn Pettis (11/16/2016)
Question, any way to get these keynotes to view later? I would like to share these with others here at work. Plus, I came in late.Actually no, that doesnt work. It gives us the current stuff, it doesn't give us what was sent out about a day ago.
Scroll down, click 'show all on demand videos' and go to the last page (11 at the moment)
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 18, 2016 at 1:15 am
TomThomson (11/17/2016)
BWFC (11/16/2016)
Sean Lange (11/15/2016)
Ed Wagner (11/15/2016)
Y.B. (11/15/2016)
Hey Brandie, cheddar is not better!! LOL (it's all personal preference of course)That being said I did recently try an Irish Cheddar which was excellent. I like something with a stronger flavor profile when it comes to cheeses...Asiago, Swiss, Oka. Although I did stray a little too far once and bought some Stinton. Ooooh boy that was something else...acquired taste for sure. Well for me anyway.
Like so many things, it depends on how you're going to use it. For example, a sharp cheddar would never be substituted for gruyere on French onion soup, but I don't know anyone who would use gruyere in a grilled cheese (croque monsieur or croque madame).
If you like strong cheeses (and I do) try a Gorgonzola. It's a type of blue cheese.
--Warning Food discussion starting--
One of my favorite ways to enjoy gorgonzola is to add it to a sauce pan with about the same amount of heavy cream. Then season with a bit of aunt and uncle (salt and pepper). Reduce to about half the volume. Then pour it over a soft polenta mixed with some fresh oregano. Talk about spectacular.
I love cheese, in fact my wife reckons that my sisters and I have a second stomach that no matter how much we've eaten already, we'll find room for cheese and biscuits. Fortunately for my waistline though, said wife is not good with dairy products so we rarely have cheese in the house. I wouldn't trust myself to buy a pound of good cheddar and not scoff the lot on my own in a couple of
dayshours.However, there's steak on the menu for Saturday night and I think I could be tempted to try Ed's sauce...
I reckon that sauce goes better with king-prawns than with steak. Perhaps it might be improved by adding some sliced garlic and a couple of guindillas (with the right meaning of guindilla - it's got different meanings in different places).
I wrote steak because I was so excited about the steaks that are arriving tomorrow I got carried away. I think on reflection you're right that it would probably better with something else.
What's the right meaning of guindilla? T'interweb produces lots of hits for peppers but which are the right kind of pepper?
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
November 18, 2016 at 1:27 am
BWFC (11/18/2016)
TomThomson (11/17/2016)
BWFC (11/16/2016)
Sean Lange (11/15/2016)
Ed Wagner (11/15/2016)
Y.B. (11/15/2016)
Hey Brandie, cheddar is not better!! LOL (it's all personal preference of course)That being said I did recently try an Irish Cheddar which was excellent. I like something with a stronger flavor profile when it comes to cheeses...Asiago, Swiss, Oka. Although I did stray a little too far once and bought some Stinton. Ooooh boy that was something else...acquired taste for sure. Well for me anyway.
Like so many things, it depends on how you're going to use it. For example, a sharp cheddar would never be substituted for gruyere on French onion soup, but I don't know anyone who would use gruyere in a grilled cheese (croque monsieur or croque madame).
If you like strong cheeses (and I do) try a Gorgonzola. It's a type of blue cheese.
--Warning Food discussion starting--
One of my favorite ways to enjoy gorgonzola is to add it to a sauce pan with about the same amount of heavy cream. Then season with a bit of aunt and uncle (salt and pepper). Reduce to about half the volume. Then pour it over a soft polenta mixed with some fresh oregano. Talk about spectacular.
I love cheese, in fact my wife reckons that my sisters and I have a second stomach that no matter how much we've eaten already, we'll find room for cheese and biscuits. Fortunately for my waistline though, said wife is not good with dairy products so we rarely have cheese in the house. I wouldn't trust myself to buy a pound of good cheddar and not scoff the lot on my own in a couple of
dayshours.However, there's steak on the menu for Saturday night and I think I could be tempted to try Ed's sauce...
I reckon that sauce goes better with king-prawns than with steak. Perhaps it might be improved by adding some sliced garlic and a couple of guindillas (with the right meaning of guindilla - it's got different meanings in different places).
I wrote steak because I was so excited about the steaks that are arriving tomorrow I got carried away. I think on reflection you're right that it would probably better with something else.
What's the right meaning of guindilla? T'interweb produces lots of hits for peppers but which are the right kind of pepper?
AFAIK, Guindilla or rather Guindilla de Ibarra is a common name for variety of Basque chilli peppers.
😎
Viewing 15 posts - 56,671 through 56,685 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply