Most DBAs have fallen into step with Powershell via running scripts to manage the SQL Server instances . The first script I wrote in 2008 – to parse SQL Server Error Logs – and return anything interesting , is an example of such a maintenance script, but I didn't start learning Powershell in-depth until I revised my approach to learning Powershell.

I’ve since written a whole bunch of Powershell scripts and use Powershell for all sorts of maintenance and automation tasks.

It was until I decided to get deeper into Powershell and invest some serious time in learning that I realized a similar approach is required as learning SQL Server - using BOL.

So I decided to focus and explore on three Powershell cmdlets – that are the gateway to exploring Powershell and getting into the flexibility and power.