PowerShell for DBAs

Richard's profileRichard Siddaway's BlogPhotosBlogLists

< Previous Next >

April 19

Chad has a very interesting post on “The Value Proposition of PowerShell to DBAs” - http://chadwickmiller.spaces.live.com/blog/cns!EA42395138308430!347.entry where he discusses the results of a poll of DBAs regarding PowerShell.

On initial reading it is a bit depressing for the PowerShell community as only 20% of respondents were using PowerShell. However, it gets a bit more cheerful if you consider that another 40% were planning to – I wonder how that will change as SQL Server 2008, with PowerShell built in, becomes more widespread.

Chad gives a number of benefits of learning PowerShell. I think that one of the most compelling reasons si that it will be a part of all future Microsoft products – look what is happening with Windows 2008 R2 – an provides a common automation platform across your Microsoft estate. PowerShell gives us the possibility of integrated, automated administration across you servers and applications.

Gives us more time for PowerShel space invaders

Technorati Tags: PowerShell

8:29 PM | Blog it | PowerShell and SQL Server

Comments (2)

To add a comment, sign in with your Windows Live ID (if you use Hotmail, Messenger, or Xbox LIVE, you have a Windows Live ID). Sign in

Don't have a Windows Live ID? Sign up

Richard Siddawaywrote:

Your point about a common scripting language is really important - it extends to a common approach as well. Using Powershell across the servers, applications and other devices gives us a chance to spread the knowledge. If you understand how its been done you only have to learn what is being done ie what the individual cmdlets are doing

I've said before that I think people who don't learn PowerShell will be at a disadvantage. Just look at whats happening with Windows 2008 R2 and Exchnage 2010

Apr. 22

Chad Millerwrote:

You bring up some good points. Using your refernce to common automation as a basis, I can see a direct benefit to DBAs in being able to leverage and share common Powershell scripts across administration groups (Storage, Server, DBA, etc.). As an example I use some EMC scripts which were originally written in T-SQL xp_cmdshell. This was done because the DBA at the time only knew T-SQL. The problem is the scripts are not usuable by Storage or Server administration groups, however if the scripts were written in Powershell we would instantly have common scripting language, Powershell, which can be used and understood by any administration group. The T-SQL version is only usable by the DBA group.

Apr. 22

Trackbacks

The trackback URL for this entry is:

http://richardsiddaway.spaces.live.com/blog/cns!43CFA46A74CF3E96!2235.trak

Weblogs that reference this entry

None