What additional scripting languages useful?

Question

What additional scripting languages useful?

Jason-543408

Valued Member

Points: 57
More actions
December 3, 2007 at 2:24 pm

#377285

I am new to SQL Server (and this forum) and was wondering what scripting languages would be useful to know in regards to administrating SQL Server 2005 (in combination w/ T-SQL)? That may be a loaded question as there are many and each one could probably get the job done but what is most common/useful/marketable when working with SS?
Thanks,
Jason

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004434 More actions · Answer 1

Dunno about others... but I've not needed anything but T-SQL with occasional trips through xp_CmdShell to use some "DOS" functionality.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Grant Fritchey SSC Guru Points: 398911 More actions · Answer 2

99.999% TSQL.

The remaining bits I use C# or VB.NET through the SMO (SQL Management Object). Very little need for anything else.

I did go through a great book on using PERL to help administer SQL Server (forget the title, it's out there) but it actually did little that I couldn't already do with TSQL. The bits it did do, I've done with C# and frankly, C# was a hell of a lot easier to program in than PERL.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 3

It also depends on what you call "additional languages". A lot of us play squarely on the OLTP side of the fence, leaving the analyticals, cubes, etc... largely alone. All of THAT fun stuff is a whole different language to me, different concepts, different behavior.....

Considering you're talking 2005 - I'd have to say CLR (either C# or VB) MIGHT be useful given its heavy integration on rare occasions while within SQL Server. It actually gets even MORE useful if you need to fix/parse/clean up data BEFORE you bring it into SQL server, or you need to interact heavily with the OS or the "outside world" for some reason.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

PW-201837 SSC-Insane Points: 20805 More actions · Answer 4

I'm currently learning & using Windows Powershell for some SQL admin/maintenance tasks.

Next version of SQL (2008) will supposedly have increased Powershell support.

Jason-543408 Valued Member Points: 57 More actions · Answer 5

Thanks everyone for your replies, that helped. Looks like T-SQL is the way to go for most tasks but could be helpful to learn VB.NET or C# in case that need arises... never hurts to learn more skills.

Thanks again!

Jason