November 21, 2016 at 8:55 am
Out for a few days, but I'm back.
WRT the PoSh instead of the Command Prompt, I'm not sure there's a big issue here. Most everything I do in cmd seems to work in the PoSh. Aliases or just native commands work. I'd guess that cmd.exe would alias to PowerShell.exe, but I would think xp_cmdshell would just work.
Personally, I'd like to see an integrated shell, as long as it's backwards compatible.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
November 21, 2016 at 9:06 am
Steve Jones - SSC Editor (11/21/2016)
Out for a few days, but I'm back.WRT the PoSh instead of the Command Prompt, I'm not sure there's a big issue here. Most everything I do in cmd seems to work in the PoSh. Aliases or just native commands work. I'd guess that cmd.exe would alias to PowerShell.exe, but I would think xp_cmdshell would just work.
Personally, I'd like to see an integrated shell, as long as it's backwards compatible.
I think this is a good change, have been using bash and PoSh instead of cmd for a long time, far superior and easier to use. Bash on Win10 is absolutely brilliant although there still are few issues but hey ho, nothing is perfect and having commands like grep is priceless!
😎
November 21, 2016 at 9:09 am
CMD / Powershell change in Win 10 I don't think has been well reported.
My understanding is that the only change is that the "cmd" command & the icon on the start menu open up a powershell window by default. This can be changed back to run command.com as now.
More importantly: The change is only in the latest build available in the _Windows Insider Program_, and Microsoft is actively courting feedback on it.
Relax everyone 🙂
(Personally, I love powershell, so I'm not too worried either way :cool:)
November 21, 2016 at 9:10 am
Eirikur Eiriksson (11/21/2016)
Steve Jones - SSC Editor (11/21/2016)
Out for a few days, but I'm back.WRT the PoSh instead of the Command Prompt, I'm not sure there's a big issue here. Most everything I do in cmd seems to work in the PoSh. Aliases or just native commands work. I'd guess that cmd.exe would alias to PowerShell.exe, but I would think xp_cmdshell would just work.
Personally, I'd like to see an integrated shell, as long as it's backwards compatible.
I think this is a good change, have been using bash and PoSh instead of cmd for a long time, far superior and easier to use. Bash on Win10 is absolutely brilliant although there still are few issues but hey ho, nothing is perfect and having commands like grep is priceless!
😎
I have to disagree with the "far superior" and "easier to use" notions, especially for the stuff that I do. Heh... and to make life easier thanks to the output from xp_CmdShell that can easily be captured, in the rare instances where I do need to use PoSh, I call it from xp_CmdShell.
--Jeff Moden
November 21, 2016 at 9:13 am
Gazareth (11/21/2016)
CMD / Powershell change in Win 10 I don't think has been well reported.My understanding is that the only change is that the "cmd" command & the icon on the start menu open up a powershell window by default. This can be changed back to run command.com as now.
More importantly: The change is only in the latest build available in the _Windows Insider Program_, and Microsoft is actively courting feedback on it.
Relax everyone 🙂
(Personally, I love powershell, so I'm not too worried either way :cool:)
Yeah... relax... and put this blindfold on. It won't hurt.
I'm not so concerned with their little dance of defaults. What I'm concerned about is some idiot at MS driving towards the someday elimination of CMD.exe and the ability to get to it from SQL Server.
--Jeff Moden
November 21, 2016 at 9:37 am
Jeff Moden (11/21/2016)
Yeah... relax... and put this blindfold on. It won't hurt.
Isn't that what they say when they put someone in front of a firing squad?
I'm not so concerned with their little dance of defaults. What I'm concerned about is some idiot at MS driving towards the someday elimination of CMD.exe and the ability to get to it from SQL Server.
Agreed. Making it unavailable will be a huge pain for things that have been written. Because it's technically the OS and not SQL, it means they wouldn't have to go with their usual minimum of 2 major releases before removing it. I don't know if that's an official policy or not, but intentionally removing functionality would be a great case for not upgrading.
November 21, 2016 at 9:43 am
Ed Wagner (11/21/2016)
Jeff Moden (11/21/2016)
Yeah... relax... and put this blindfold on. It won't hurt.Isn't that what they say when they put someone in front of a firing squad?
Or a wedding...
~~~~\o/~~~/\~~~
😎
November 21, 2016 at 9:49 am
Ed Wagner (11/21/2016)
Jeff Moden (11/21/2016)
Yeah... relax... and put this blindfold on. It won't hurt.Isn't that what they say when they put someone in front of a firing squad?
I'm not so concerned with their little dance of defaults. What I'm concerned about is some idiot at MS driving towards the someday elimination of CMD.exe and the ability to get to it from SQL Server.
Agreed. Making it unavailable will be a huge pain for things that have been written. Because it's technically the OS and not SQL, it means they wouldn't have to go with their usual minimum of 2 major releases before removing it. I don't know if that's an official policy or not, but intentionally removing functionality would be a great case for not upgrading.
I doubt MS would simply remove cmd support overnight as it is a part of the OS not SQL Server and the ramifications of removing it would be pretty huge for every person who works with windows in any kind of administrative role. That said I wouldn't be surprised if MS moved to make powershell the default console language as it is newer and yes has more functionality than the old cmd.
I also see this as a separate issue than xp_cmdshell as that's just a plugin to send console commands to the OS, despite its name it's not intrinsically tied to cmd and if powershell was the default console language I'd imagine it would work just as well.
November 21, 2016 at 10:12 am
WayneS (11/21/2016)
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.
You don't have to update version by version. You can go from any 2005+ to latest in one step, using backup/restore (preferred method) or detach/attach. Don't believe me? Check out what Paul Randal says about it here[/url].
If you are on 2000 or earlier, beside my sympathies, you will first need to get up to 2005 in order to do this.
Me not knowing better, I used backup/restore for my test system (2008R2 to 2016). Worked so did not think anything about it. Have not found any old code that does not work but I am not though testing.
November 21, 2016 at 10:25 am
djj (11/21/2016)
WayneS (11/21/2016)
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.
You don't have to update version by version. You can go from any 2005+ to latest in one step, using backup/restore (preferred method) or detach/attach. Don't believe me? Check out what Paul Randal says about it here[/url].
If you are on 2000 or earlier, beside my sympathies, you will first need to get up to 2005 in order to do this.
Me not knowing better, I used backup/restore for my test system (2008R2 to 2016). Worked so did not think anything about it. Have not found any old code that does not work but I am not though testing.
Have you upped the compatibility level?
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.
November 21, 2016 at 11:23 am
Gazareth (11/21/2016)
CMD / Powershell change in Win 10 I don't think has been well reported.My understanding is that the only change is that the "cmd" command & the icon on the start menu open up a powershell window by default. This can be changed back to run command.com as now.
More importantly: The change is only in the latest build available in the _Windows Insider Program_, and Microsoft is actively courting feedback on it.
Relax everyone 🙂
(Personally, I love powershell, so I'm not too worried either way :cool:)
The way I read the initial article, it referred to Windows 10 Create. Isn't that the third party developer version? Or am I missing something?
November 21, 2016 at 11:46 am
Brandie Tarvin (11/21/2016)
Gazareth (11/21/2016)
CMD / Powershell change in Win 10 I don't think has been well reported.My understanding is that the only change is that the "cmd" command & the icon on the start menu open up a powershell window by default. This can be changed back to run command.com as now.
More importantly: The change is only in the latest build available in the _Windows Insider Program_, and Microsoft is actively courting feedback on it.
Relax everyone 🙂
(Personally, I love powershell, so I'm not too worried either way :cool:)
The way I read the initial article, it referred to Windows 10 Create. Isn't that the third party developer version? Or am I missing something?
Yeah Windows Insider Program, same thing AFAIK.
Jeff, someday we'll get you to stop worrying & love the PoSh. You'll be riding that pipeline in like Slim Pickens 😉
November 22, 2016 at 4:59 am
WayneS (11/21/2016)
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.
You don't have to update version by version. You can go from any 2005+ to latest in one step, using backup/restore (preferred method) or detach/attach. Don't believe me? Check out what Paul Randal says about it here[/url].
If you are on 2000 or earlier, beside my sympathies, you will first need to get up to 2005 in order to do this.
I know that I don't need to do all those.
I was just counting out the number of versions that my client is behind.
November 22, 2016 at 5:17 am
Phil Parkin (11/21/2016)
Have you upped the compatibility level?
All but one which I have now changed. :ermm:
November 22, 2016 at 7:30 am
Hugo Kornelis (11/22/2016)
WayneS (11/21/2016)
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.
You don't have to update version by version. You can go from any 2005+ to latest in one step, using backup/restore (preferred method) or detach/attach. Don't believe me? Check out what Paul Randal says about it here[/url].
If you are on 2000 or earlier, beside my sympathies, you will first need to get up to 2005 in order to do this.
I know that I don't need to do all those.
I was just counting out the number of versions that my client is behind.
I see. I guess the "2005 --> 2008" ... made it look to me like upgrading version by version.
I'll resume lurking now.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
Viewing 15 posts - 56,731 through 56,745 (of 66,000 total)
You must be logged in to reply to this topic. Login to reply