Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

Scripting Expand / Collapse
Posted Thursday, September 26, 2013 11:19 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Wednesday, November 30, 2016 3:59 PM
Points: 660, Visits: 1,444
I think PowerShell is very cool but I've only ever had a use for it once. I use it to clean up my backup directories. There is just too much to learn and now that M$ has lost control of all the markets it's hard to know where to spend your time. Scripting seems like a lower priority to me.
Post #1498970
Posted Thursday, September 26, 2013 11:19 AM



Group: Administrators
Last Login: Yesterday @ 3:36 PM
Points: 34,362, Visits: 18,572
Craig-315134 (9/26/2013)
Steve Jones wrote:

... I am starting to think that Powershell might be the best investment in my future skills.

Steve, do you think Powershell would also be a good skill for application developers to learn, please?


I do, only because as you look to make changes to your environment or deploy changes, scripting ensures consistency and can be packaged up with your project as something else to run in an MSBuild-type script.

Note that I think PoSh is trivial to learn for developers. It's essentially procedural programming with object handles. Piece of cake if you are used to VS development.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1498971
Posted Thursday, September 26, 2013 11:28 AM

Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, May 4, 2016 11:58 AM
Points: 391, Visits: 971
Thanks, Steve.

I don't use MS application development tools or languages any more (Mr Hanrahan's previous post is an indication of the times, including those in our shop), so I'm not sure if PS would prove terribly useful that regard. But SQL Server will be around for the foreseeable future, so it still would have some utility for us.


Post #1498976
Posted Thursday, September 26, 2013 1:34 PM

Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 7:31 AM
Points: 506, Visits: 5,406
Dave Schutz (9/26/2013)
I've just started working with PowerShell and I save my scripts in Notepad so I can comment them. Otherwise I'll forget what I created the script for. Scripting is the new future of IT.

What about some kind of database ... <runs>. TFS (or similar - other source control systems are available), then as well as searchable documentation you can add in any tests etc. you want to have with them

I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
Post #1499041
Posted Sunday, September 29, 2013 7:10 AM

SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Yesterday @ 9:19 AM
Points: 9,822, Visits: 11,891
Sure, we all need to be able to write scripts; that's been true quite independent of Sql Server or indeed of the existence of relational databases for a very long time. what changes is which scripting languages one needs to know.
Back in the SQL Server 2000 days, it was easy to get by with T-SQL scripts, CMDEXEC scripts, and Active-X scripts (which in my case meant JScript scripts; I never bothered to find out if SQL Agent would allow VBScript, because I dislike the language) and SQL Server Agent supported all three. I haven't come across anything much I couldn't handle with one of those (particularly as it's easy to make calls between JScript and CMDEXEC Script or from either to T-SQL) although I occassionally used other things without bothering to learn them properly because the uses were pretty well one-offs. As for Powershell, which is one of the scripting languages that I've I've used but never bothered to learn properly because I didn't expect to use it enough to make the investment of time to learn it worth while, I suppose it may become necessary sometime because MS have deprecated the Active-X capability of SQL Agent, but given that the Active-X capabiliy is going to continue to be available in at least the next two releases there are probably quite a few of us who may not have to worry about it.

My wory is that dropping the Active-X subsystem and using Powershell instead may not be a step forwards. Is it just churn for churn's sake? Or does it really provide new capability or make scripting easier?

Post #1499748
Posted Monday, September 30, 2013 10:07 AM


Group: General Forum Members
Last Login: Tuesday, January 26, 2016 9:10 AM
Points: 2,602, Visits: 1,694
Sorry to come to the ball late but I also agree but in a slightly different approach. As a developer I write code. .Net C# code and I use SSIS, SSRS, SSAS and whatever else I can find that will make it happen. But these are code components. As a rule I choose to use these first and foremost. They are far and away my first choice. But some of the time I find that my first choice solution is not elegant nor easily developed. Kind of like the case where you try to pound a nail with a screwdriver. Great tool, easy task but not made for this at all.

In screwdriver cases I need to use my second choice. It just works better that way.

For those who are scriptors who know scripts like some developers know their language of choice, break out the scripting tools and let it rip until you need to execute a second choice. It works better that was as well.

Until people learn this we, will see intelligent folks yelling and screaming as they continue to pound those nails with their screwdrivers.

Not all gray hairs are Dinosaurs!
Post #1500092
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse