Compare hotfix

Easy way to compare hotfix

The Poster of the Plethora of PowerShell Pitfalls

One of the downsides of learning a new computer language is that transfer of training doesn't always work to your advantage. In fact, the habits you picked up in the past may now cause confusion. In this poster or wall-chart for long walls, Michael Sorens selects the thirty-six most common causes of confusion for anyone getting to grips with PowerShell.

Powershell day-to-day Admin tasks: WMI, CIM and PSWA

WMI (Windows Management Instrumentation) is the basic way of querying and changing basic information about any windows server, including SQL Server or Exchange Server. It provides a logical structure and representation of systems and services that are hosted on the server and is essential for anyone who is keen to automate routine monitoring and administration work via PowerShell, especially where many servers are involved in the task.

A Plethora of PowerShell Pitfalls: Part 2

There are some pitfalls in PowerShell for the unwary. Many people who are learning PowerShell come across quirks that can cause frustration. Michael Sorens continues his series, warning abut four of the most common PowerShell pitfalls and explains how to avoid them.

Server Logins

Generate password using PowerShell

If you want to generate temporary passwords, can use my script.

Different ways to find Powershell Version

Check running SQL Services

Check all the running SQL services in different servers.
You can use the details before you start implementing SQL Patch to the servers i.e. if you want to explicitly stop the SQL Services.

Check Existence of Server and find Instance Type

Execute the function and pass only the SQL Server Name to check if the SQL Instance is available and if yes, what is the Instance Type.

Run a specific query across all servers using powershell

Run a specific query across all servers using powershell