August 17, 2015 at 8:45 pm
Comments posted to this topic are about the item Changing roles
August 18, 2015 at 12:42 am
The correct answer is "It Depends" on which version of SQL Server you're using. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2015 at 3:43 am
Nice question, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 18, 2015 at 3:44 am
Jeff Moden (8/18/2015)
The correct answer is "It Depends" on which version of SQL Server you're using. 😉
When not explicitly mentioned, the last version that is publicly available.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 18, 2015 at 5:14 am
Koen Verbeeck (8/18/2015)
Jeff Moden (8/18/2015)
The correct answer is "It Depends" on which version of SQL Server you're using. 😉When not explicitly mentioned, the last version that is publicly available.
That's the exact thought process I went through. Then it became pretty simple.
August 18, 2015 at 6:17 am
Good question 🙂
Regards
ld
Stoke-on-Trent
United Kingdom
If at first you don't succeed, go to the pub and drink away your current thought plan.
August 18, 2015 at 8:30 am
Thanks for the question. It's not something I've used.
August 18, 2015 at 9:18 am
Koen Verbeeck (8/18/2015)
Jeff Moden (8/18/2015)
The correct answer is "It Depends" on which version of SQL Server you're using. 😉When not explicitly mentioned, the last version that is publicly available.
Well, since that is a CTP, things could change any day. 😉
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 18, 2015 at 9:51 am
Koen Verbeeck (8/18/2015)
Jeff Moden (8/18/2015)
The correct answer is "It Depends" on which version of SQL Server you're using. 😉When not explicitly mentioned, the last version that is publicly available.
Heh... yeah... I know that but let's just suppose that they make another change in the future where the correct answer for the current "latest version" is no longer the correct answer for the question. I think that all these questions should have the version of SQL appropriate for the question be listed in the question.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2015 at 11:09 am
Jeff Moden (8/18/2015)
Koen Verbeeck (8/18/2015)
Jeff Moden (8/18/2015)
The correct answer is "It Depends" on which version of SQL Server you're using. 😉When not explicitly mentioned, the last version that is publicly available.
Heh... yeah... I know that but let's just suppose that they make another change in the future where the correct answer for the current "latest version" is no longer the correct answer for the question. I think that all these questions should have the version of SQL appropriate for the question be listed in the question.
You can always tie the question to the publicly available version by date - after all, it is a question of the day. That also implies that the version should always be specified for previews.
This point may eventually become confusing if MSFT extends the "software as a service" model to SQLS and you will deal with - perish the thought - a continuously updated SQL Server 365.
Thanks to Steve for the question and to everyone for the discussion!
August 18, 2015 at 11:21 pm
This was removed by the editor as SPAM
August 19, 2015 at 7:25 am
Revenant (8/18/2015)
Jeff Moden (8/18/2015)
Koen Verbeeck (8/18/2015)
Jeff Moden (8/18/2015)
The correct answer is "It Depends" on which version of SQL Server you're using. 😉When not explicitly mentioned, the last version that is publicly available.
Heh... yeah... I know that but let's just suppose that they make another change in the future where the correct answer for the current "latest version" is no longer the correct answer for the question. I think that all these questions should have the version of SQL appropriate for the question be listed in the question.
You can always tie the question to the publicly available version by date - after all, it is a question of the day. That also implies that the version should always be specified for previews.
This point may eventually become confusing if MSFT extends the "software as a service" model to SQLS and you will deal with - perish the thought - a continuously updated SQL Server 365.
Thanks to Steve for the question and to everyone for the discussion!
It would be a whole lot easier if people would just put the version number on their questions. "Version: 2014 EE". How hard is that?
Shifting gears a bit, just imagine if SQL Server were continuously updated. Instead of the occasion significant and well publicized bombs like 2014 SP1, there would be daily knife cuts to the very fabric of your business. Imagine trying to troubleshoot such a thing. No thank you!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2015 at 3:44 am
Easy question as the possibilty to add/remove members to database roles was introduced in SQL Server 2012. So the question about the version is useless as ( if I am not going wrong ) I usually am replying with my knowlegdes concerning the supported versions ( 2012/2014 ).
2016 is only in CTP state and when the question is related to this version , I am considering only the last available level of the CTP.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply