Is Vanilla Powershell Enough of a Language for Windows & DB Server Admins?
As a DBA in an instead huge setting, my point of view is YES. We have actually constructed a whole MS SQL Server display and also upkeep structure making use of just PowerShell 1.0. This system automates day-to-day ability surveillance along with automating backup index upkeep etc
I've actually located the Quest ActiveRoles break - in to be really valuable for collaborating with and also taking care of Active Directory. You can get the breeze - in here, yet I assume this blog post does a superb work clarifying what it is, just how to set it up, and also just how to utilize it.
By itself and also by yourself, PowerShell is not nearly enough.
Yet PowerShell is not the only one, and also neither are you. There are expansions such as John D. Cook states above, along with a vivid area sharing what they learn more about it.
It's made to be conveniently and also frequently expanded, and also offers you accessibility to COM and.NET things essential to carry out whatever you such as.
To address this inquiry, you require to zoom bent on the larger image and also ask what it suggests to carry out Windows and also SQL Servers. As an example, the amount of of these various other points do you have in your setting :
- Third event back-up items like NetBackup or BackupExec
- Antivirus items
- Storage devices
- Firewalls or internet filtering system software program
- Hardware signaling (like IBM Director or HP SIM)
All of these points have their very own devices for monitoring, and also given that PowerShell is still reasonably new, not all solutions will certainly be PowerShell - made it possible for. In the meantime, you might require to leap out of PowerShell in order to take care of points like those.
On the other side, there's nothing else language that functions much better throughout every one of those Windows devices either.
When you claim "capability to carry out web servers", that does not originate from a Windows language yet. In the *nix globe, you can remain inside a scripting setting, yet the Windows globe isn't fairly there yet.
The response to your first inquiry is an unquestionable "YES".
To take care of an existing Windows domain name, "vanilla" PowerShell (no added snapins) gives out of package assistance for WMI, ADSI, COM, and.NET.
Taking care of remote equipments is taken care of via WMI (or COM/. NET relying on the usage instance).
Taking care of SQL Server can make use of the SMO collections (see the SQL Server PowerShell Extensions for suggestions). You can access information using ADO.NET.
To address the 2nd component of your inquiry, regarding what are excellent 3rd party addons, actually relies on what you require to do. As John Cook stated, the PowerShell Community Extensions are a wonderful basic enhancement. There are several, several others. PowerShellCommunity.Org has a variety of wonderful referrals for 3rd party items and also Codeplex has a multitude of open resource PowerShell tasks.
Even more Microsoft items are including PowerShell assistance (like SQL Server 2008, Exchange, Active Directory, and so on)
V2 (which is coming up to) has some wonderful remoting and also history work capacities.
Powershell does not deliver with SQL management devices, although you can remain to make use of points like osql or isql. I recognize there are Powershell addins that allow you "place" a SQL server and also browse it like it was a documents system (just like the Registry things that's constructed in).