youdidwhatwithtsql.com » Powershell

Check Mirroring Status with Powershell

Rhys — Tue, 31 Jan 2012 12:21:23 +0000

Here’s a simple Powershell snippet to check the mirroring status on your SQL Server instances.

# Load SMO extension
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | Out-Null;
 
# Servers to check
$sqlservers = @("server1", "server2", "server3");
foreach($server in $sqlservers)
{
	$srv = New-Object "Microsoft.SqlServer.Management.Smo.Server" $server;
	# Get mirrored databases
	$databases = $srv.Databases | Where-Object {$_.IsMirroringEnabled -eq $true}; 
	Write-Host $server;
	Write-Host "==================================";
	$databases | Select-Object -Property Name, MirroringStatus | Format-Table -AutoSize;
}

This will output something looking like below…

server1
====================================

Name                 MirroringStatus
----                 ---------------
db1         		Synchronized
db2                    	Synchronized
db3              	Synchronized
db4			Synchronized
db5    			Synchronized
server2
=====================================

Name                 MirroringStatus
----                 ---------------
db1         		Synchronized
db2                    	Synchronized
db3              	Synchronized
db4			Synchronized
db5    			Synchronized
server3
=====================================

Name                 MirroringStatus
----                 ---------------
db1         		Synchronized
db2                    	Synchronized
db3              	Synchronized
db4			Synchronized
db5    			Synchronized

Post from: youdidwhatwithtsql.com

Check Mirroring Status with Powershell

Beware the Powershell -Contains operator

Rhys — Tue, 29 Nov 2011 12:20:00 +0000

Many of us tend to jump quickly, into a new programming or scripting language, applying knowledge we’ve learned elsewhere to the current task at hand. Broadly speaking this works well but these always a little gotcha to trip you up!

A good example is the Powershell -contains operator. It’s not like .Net String.Contains method as you might first think.

^?View Code POWERSHELL

$var = "Rhys Campbell";
$var -contains "Rhys";

The result of this is false. Why? Because the -contains operator in Powershell is used for testing for items in an array.

^?View Code POWERSHELL

$var = "Rhys Campbell", "Joe Bloggs";
$var -contains "Rhys Campbell";

Will return true, but;

^?View Code POWERSHELL

$var -contains "Rhys*";

Will return false as wildcards will not work as we assume they will. For wildcard matching we can use the -match operator.

^?View Code POWERSHELL

$var = "Rhys Campbell";
$var -match "Rhys";

This will return true when matching simple strings or the matching items from an array of strings. Now I’m going to try and remember what assumption is the mother of (NSFW, contains cussing).

Post from: youdidwhatwithtsql.com

Beware the Powershell -Contains operator

Monitoring SSRS Subscriptions with Powershell

Rhys — Fri, 25 Nov 2011 13:17:09 +0000

We don’t use SSRS much at my workplace but its usage is slowly creeping up. I realised that none of us are keeping an eye on the few subscriptions we have set-up. So I decided to do something about that.

Here’s a bit of Powershell code that uses the SSRS Web Service to pull out a list of subscriptions from SSRS and print out some information to the screen. As always I try to bring problems to attention with a little red text so you can identify any failed subscriptions. There’s a few assumptions in the script, so be sure to read the comments, and it’s a far from complete and fully tested script. Just a little something to get me started onto something better.

^?View Code POWERSHELL

# If you use multiple ssrs server just stick in another foreach loop
# and iterate over an array of ssrs server names.
$reportserver = "sqlserver";
$url = "http://$($reportserver)/reportserver/reportservice.asmx?WSDL";
 
$ssrs = New-WebServiceProxy -uri $url -UseDefaultCredential -Namespace "ReportingWebService";
 
# Uncomment to list all available methods & properties in the ssrs web service...
#$ssrs | Get-Member;
 
# Get datasources (assumes default path to folder)
$datasources = $ssrs.ListChildren("/Data Sources", $true);
 
# for each datasource
foreach($ds in $datasources)
{
	# Get reports
	$reports = $ssrs.ListReportsUsingDataSource($ds.Path);
	# For each report
	foreach($r in $reports)
	{
		# Get all subscriptions
		$subscriptions = $ssrs.ListSubscriptions($r.Path, $r.Owner);
		# foreach subscription
		foreach($s in $subscriptions)
		{
			# Uncomment to view more subscription methods & properties
			# $s | Get-Member;
			# Probably missing a few important keywords here...
			$colour = "Green";
			if($s.Status -match "Failure" -or $s.Status -match "Error")
			{
				$colour = "Red";
			}
			Write-Host -ForegroundColor $colour $s.Report $s.Status $s.LastExecuted | Format-Table -AutoSize;
		}
	}
}

After running this script successfully you should be something like below;

Post from: youdidwhatwithtsql.com

Monitoring SSRS Subscriptions with Powershell

Testing a Failover Cluster with Powershell

Rhys — Thu, 03 Nov 2011 11:26:22 +0000

Just a quick Powershell snippet that I’m going to use to run validation tests on one of my staging Failover Clusters during OOH.

The script below will take some services offline, run the validation tests, before bringing the appropriate cluster groups back online. The report will be saved using the date as the name. To use this you will need to set $cluster appropriately and perhaps customize the cluster groups that are brought offline & online.

^?View Code POWERSHELL

Import-Module FailoverClusters;
 
# Set cluster name
$cluster = "Cluster";
 
# Date stamp used for report name
$date = Get-Date -Format "yyyyMMdd";
 
# Take cluster services offline. You may need to customise this
# according to your specific needs
Stop-ClusterGroup -Cluster $cluster -Name "ClusterDtc";
Stop-ClusterGroup -Cluster $cluster -Name "SQL Server (MSSQLSERVER)";
 
# Test Cluster
Test-Cluster -Cluster $cluster -ReportName "$date";
 
# Bring services back online
Start-ClusterGroup -Cluster $cluster -Name "ClusterDtc";
Start-ClusterGroup -Cluster $cluster -Name "SQL Server (MSSQLSERVER)";

The output will look something like below…

Name                       OwnerNode                                      State
----                       ---------                                      -----
ClusterDtc            	   Node1                                 	  Offline
SQL Server (MSSQLSERVER)   Node1                                 	  Offline
WARNING: Cluster Configuration - Validate Resource Status: The test reported
some warnings..
WARNING: Network - Validate IP Configuration: The test reported some warnings..
WARNING:
Test Result:
ClusterConditionallyApproved
Testing has completed successfully. The configuration appears to be suitable
for clustering.  However, you should review the report because it may contain
warnings which you should address to attain the highest availability.
Test report file path: C:\Users\ClusterAdmin\AppData\Local\Temp\20111103.mht
20111103.mht
ClusterDtc            	   Node1                                 	 Online
SQL Server (MSSQLSERVER)   Node1                                 	 Online

Post from: youdidwhatwithtsql.com

Testing a Failover Cluster with Powershell

Domain user password expiry with Powershell

Rhys — Thu, 13 Oct 2011 11:14:17 +0000

I needed to figure out a method for producing alerts when a domain account is approaching the password reset date. Here it is in a few lines of Powershell…

^?View Code POWERSHELL

# Set name here
$name = "Rhys Campbell";
$user = Get-ADUser -LDAPFilter "(Name=$name)" -Properties PasswordLastSet;
$days = $(Get-ADDefaultDomainPasswordPolicy).MaxPasswordAge;
$expires = $user.PasswordLastSet + $days;
$days_left = $expires - $(Get-Date);
Write-Host "Password for $name expires on $expires which is in $($days_left.Days) days.";

This will display something along the lines of;

Password for Rhys Campbell expires on 11/18/2011 08:19:36 which is in 35 days.

Post from: youdidwhatwithtsql.com

Domain user password expiry with Powershell

Checking Disk alignment with Powershell

Rhys — Wed, 05 Oct 2011 19:36:04 +0000

Disk alignment has been well discussed on the web and the methods to check this always seem to use wmic or DISKPART. I’ve always loathed wmi so here’s a few lines of Powershell that achieves the same thing;

^?View Code POWERSHELL

$sqlserver = "sqlinstance";
# Get disk partitions
$partitions = Get-WmiObject -ComputerName $sqlserver -Class Win32_DiskPartition;
$partitions | Select-Object -Property DeviceId, Name, Description, BootPartition, PrimaryPartition, Index, Size, BlockSize, StartingOffset | Format-Table -AutoSize;

This will display something looking like below;

DeviceId              Name                  Description             BootPartition PrimaryPartition Index          Size BlockSize StartingOffset
--------              ----                  -----------             ------------- ---------------- -----          ---- --------- --------------
Disk #2, Partition #0 Disk #2, Partition #0 Installable File System         False             True     0 1099523162112       512        1048576
Disk #3, Partition #0 Disk #3, Partition #0 Installable File System         False             True     0  536878252032       512        1048576
Disk #4, Partition #0 Disk #4, Partition #0 Installable File System         False             True     0    1082130432       512          65536
Disk #5, Partition #0 Disk #5, Partition #0 Installable File System         False             True     0    1082130432       512          65536
Disk #1, Partition #0 Disk #1, Partition #0 Installable File System         False             True     0  107376279552       512        1048576
Disk #0, Partition #0 Disk #0, Partition #0 Installable File System          True             True     0     104857600       512        1048576
Disk #0, Partition #1 Disk #0, Partition #1 Installable File System         False             True     1   81684070400       512      105906176
Disk #0, Partition #2 Disk #0, Partition #2 Installable File System         False             True     2  104857600000       512    81789976576
Disk #0, Partition #3 Disk #0, Partition #3 Installable File System         False             True     3  104857600000       512   186647576576

A 64K cluster size is good for SQL Server. But what about the offset? The simple calculation below can be used to check this…

StartingOffset / BlockSize / 128 (a 64K cluster has 128 sectors assuming a 512 block size).

If this calculation spits out a number with any decimal places then you have some disk aligning to do.

Post from: youdidwhatwithtsql.com

Checking Disk alignment with Powershell

Fun with the Get-Hotfix cmdlet

Rhys — Mon, 15 Aug 2011 11:37:00 +0000

With the Get-Hotfix cmdlet you can query the list of hotfixes that have been applied to computers.

^?View Code POWERSHELL

Get-Hotfix | Format-Table -AutoSize;

This will display the list of hotfixes installed on the local computer.

Source Description     HotFixID  InstalledBy          InstalledOn
------ -----------     --------  -----------          -----------
SO0590 Update          982861    NT AUTHORITY\SYSTEM  07/07/2011 00:00:00
SO0590 Update          KB958830  host\Administrator   07/07/2011 00:00:00
SO0590 Update          KB958830  host\Administrator
SO0590 Update          KB971033  host\Administrator
SO0590 Update          KB2264107 NT AUTHORITY\SYSTEM  06/08/2011 00:00:00
SO0590 Security Update KB2305420 host\Administrator   03/10/2011 00:00:00
SO0590 Security Update KB2393802 host\Administrator   03/10/2011 00:00:00
SO0590 Security Update KB2425227 host\Administrator   03/10/2011 00:00:00
SO0590 Security Update KB2475792 host\Administrator   03/10/2011 00:00:00
SO0590 Security Update KB2476490 NT AUTHORITY\SYSTEM
SO0590 Security Update KB2479628 host\Administrator   03/10/2011 00:00:00
SO0590 Security Update KB2479943 host\Administrator   03/10/2011 00:00:00
SO0590 Update          KB2484033 host\Administrator   03/10/2011 00:00:00
SO0590 Security Update KB2485376 host\Administrator   03/10/2011 00:00:00
SO0590 Update          KB2487426 host\Administrator   03/10/2011 00:00:00
SO0590 Update          KB2488113 NT AUTHORITY\SYSTEM  06/09/2011 00:00:00
SO0590 Security Update KB2491683 NT AUTHORITY\SYSTEM  06/09/2011 00:00:00
SO0590 Update          KB2492386 NT AUTHORITY\SYSTEM  06/09/2011 00:00:00

Not overly impressive in itself but Powershell really comes into its own when querying multiple computers. For example you may wish to confirm that a bunch of computers all have an important hotfix installed. This script will do it. Just alter the $HotFixID and $computers as needed.

^?View Code POWERSHELL

# HotFixId to check for
$HotFixID = "KB958830";
 
# Array of computers to check
$computers = @("server1", "server2", "server3", "server4", "server5");
 
# Query each computer
foreach($computer in $computers)
{
	$hf = Get-HotFix -ComputerName $computer | Where-Object {$_.HotFixId -eq $HotFixID} | Select-Object -First 1;
	if($hf -eq $null)
	{
		Write-Host "Hotfix $HotFixID is not installed on $computer";
	}
	else
	{
		Write-Host "Hotfix $HotFixID was installed on $computer on by " $($hf.InstalledBy);
	}
}

In a few moments you can see which computers you need to take action on;

Hotfix KB958830 was installed on server1 on by  SMARTODDS\campbellr
Hotfix KB958830 was installed on server2 on by  SMARTODDS\campbellr
Hotfix KB958830 is not installed on server3
Hotfix KB958830 is not installed on server4
Hotfix KB958830 is not installed on server5

Powershell; the eliminator of tedium!

Post from: youdidwhatwithtsql.com

Fun with the Get-Hotfix cmdlet

Fun with the Get-EventLog cmdlet

Rhys — Fri, 12 Aug 2011 11:22:00 +0000

The Get-EventLog cmdlet is great for working with the Windows Event Logs on local and remote computers. It includes lots of parameters that make life much easier than using the Event Viewer GUI.

To list the available logs on the local computer just execute;

^?View Code POWERSHELL

Get-EventLog -List | Format-Table -AutoSize;

Max(K) Retain OverflowAction    Entries Log
------ ------ --------------    ------- ---
20,480      0 OverwriteAsNeeded  50,916 Application
20,480      0 OverwriteAsNeeded       0 HardwareEvents
   512      7 OverwriteOlder          0 Internet Explorer
20,480      0 OverwriteAsNeeded       0 Key Management Service
 8,192      0 OverwriteAsNeeded      52 Media Center
   128      0 OverwriteAsNeeded       3 OAlerts
                                        Security
20,480      0 OverwriteAsNeeded  56,258 System
15,360      0 OverwriteAsNeeded   2,889 Windows PowerShell

It’s great for drilling down into the Event Logs to get the information you’re most interested in. For example, this line of Powershell gets all Errors in the Application Event Log, from the last 24 hours.

^?View Code POWERSHELL

Get-EventLog -LogName Application -EntryType Error -After $(Get-Date).AddHours(-24) | Format-Table -AutoSize;

This snippet can pull out all the Event Log errors from any combination of servers and logs within the last 24 hours. Great for those morning checks!

^?View Code POWERSHELL

# Set servers to query
$servers = @("server1", "server2", "server2");
# Set event logs to query
$logs = @("System", "Application");
 
Write-Host "Querying servers for event log errors in the last 24 hours...";
Write-Host "";
 
foreach($server in $servers)
{
	Write-Host $server;
	Write-Host "====================================";
	Write-Host "";
	foreach($log in $logs)
	{
		Write-Host "$log Event Log";
		Write-Host "=================";
		Get-EventLog -ComputerName $server -LogName $log -EntryType Error -After $(Get-Date).AddHours(-24) | Format-Table -AutoSize; 
	}
}

Querying servers for event log errors in the last 24 hours...

server1
====================================

System Event Log
=================

Index Time         EntryType Source                  InstanceID Message
----- ----         --------- ------                  ---------- -------
80222 Jul 26 19:56 Error     Service Control Manager 3221232472 The VMware vCenter Converter Standalone Worker service...
80221 Jul 26 19:56 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...
80220 Jul 26 19:55 Error     Service Control Manager 3221232472 The VMware vCenter Converter Standalone Server service...
80219 Jul 26 19:55 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...
80202 Jul 26 19:55 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...

Application Event Log
=================

Index Time         EntryType Source   InstanceID Message
----- ----         --------- ------   ---------- -------
90050 Jul 26 19:56 Error     VzCdbSvc          7 Failed to load the plug-in module. (GUID = {56F9312C-C989-4E04-8C23-2...
90048 Jul 26 19:56 Error     VzCdbSvc          7 Failed to load the plug-in module. (GUID = {48512A59-C8A5-4805-9048-2...

server2
====================================

System Event Log
=================

Index Time         EntryType Source                  InstanceID Message
----- ----         --------- ------                  ---------- -------
80222 Jul 26 19:56 Error     Service Control Manager 3221232472 The VMware vCenter Converter Standalone Worker service...
80221 Jul 26 19:56 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...
80220 Jul 26 19:55 Error     Service Control Manager 3221232472 The VMware vCenter Converter Standalone Server service...
80219 Jul 26 19:55 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...
80202 Jul 26 19:55 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...

Application Event Log
=================

Index Time         EntryType Source   InstanceID Message
----- ----         --------- ------   ---------- -------
90050 Jul 26 19:56 Error     VzCdbSvc          7 Failed to load the plug-in module. (GUID = {56F9312C-C989-4E04-8C23-2...
90048 Jul 26 19:56 Error     VzCdbSvc          7 Failed to load the plug-in module. (GUID = {48512A59-C8A5-4805-9048-2...

server3
====================================

System Event Log
=================

Index Time         EntryType Source                  InstanceID Message
----- ----         --------- ------                  ---------- -------
80222 Jul 26 19:56 Error     Service Control Manager 3221232472 The VMware vCenter Converter Standalone Worker service...
80221 Jul 26 19:56 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...
80220 Jul 26 19:55 Error     Service Control Manager 3221232472 The VMware vCenter Converter Standalone Server service...
80219 Jul 26 19:55 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...
80202 Jul 26 19:55 Error     Service Control Manager 3221232481 A timeout was reached (30000 milliseconds) while waiti...

Application Event Log
=================

Index Time         EntryType Source   InstanceID Message
----- ----         --------- ------   ---------- -------
90050 Jul 26 19:56 Error     VzCdbSvc          7 Failed to load the plug-in module. (GUID = {56F9312C-C989-4E04-8C23-2...
90048 Jul 26 19:56 Error     VzCdbSvc          7 Failed to load the plug-in module. (GUID = {48512A59-C8A5-4805-9048-2...

The GUI is dead, long live Powershell!

Post from: youdidwhatwithtsql.com

Fun with the Get-EventLog cmdlet

Identify the Active Cluster Node with Powershell

Rhys — Tue, 26 Jul 2011 13:24:26 +0000

I wanted to find a way of programatically identifying the active node of a SQL Server Cluster. I found this post that demonstrated how to do it with TSQL. As I love Powershell so much here’s another method to do it;

^?View Code POWERSHELL

# Set cluster name 
$cluster_name = "ClusterName";
# Load SMO extension
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | out-null;
$srv = New-Object "Microsoft.SqlServer.Management.Smo.Server" $cluster_name;
# Get server properties
$properties = $srv.Properties
$owner_node = $properties.Item("ComputerNamePhysicalNetBIOS").Value;
$is_clustered = $properties.Item("IsClustered").Value
if($is_clustered)
{
	Write-Host "The current active node of $cluster_name is $owner_node.";
}
else
{
	Write-Host "$cluster_name is not a clustered instance of SQL Server.";
}

Execute against your cluster and it will tell you which is the current active node.

The current active node of ClusterName is Node1.

It will also tell you if the instance you’re executing against isn’t a cluster.

NotACluster is not a clustered instance of SQL Server.

Post from: youdidwhatwithtsql.com

Identify the Active Cluster Node with Powershell

Failover All Cluster Resources With Powershell

Rhys — Fri, 22 Jul 2011 12:03:45 +0000

Here’s a simple example showing how to manage the failover process with Powershell, making sure all resources are running on one node. First, execute the below command to show which node owns the resources.

^?View Code POWERSHELL

Get-ClusterGroup -Cluster ClusterName | Format-Table -AutoSize;

Name              OwnerNode     State
----              ---------     -----
SoStagSQL20Dtc    Node1 	Online
SQL Server        Node1 	Online
Cluster Group     Node1 	Online
Available Storage Node1 	Online

In this example all services are currently running on Node1. It’s a simple Powershell one-liner to failover everything to another node. The following example assumes a 2 node cluster and all services will be failed over to the other node;

^?View Code POWERSHELL

Get-ClusterNode -Cluster ClusterName -Name Node1 | Get-ClusterGroup | Move-ClusterGroup | Format-Table -Autosize;

All services are now running on Node2

Name			OwnerNode	State
----			---------	-----
SoStagSQL20Dtc		Node2		Online
SQL Server		Node2		Online
Cluster Group		Node2		Online
Available Storage	Node2		Online

If you have more than 2 nodes in the cluster you can use the -Name parameter of the Move-ClusterGroup to specify a node to move resources to.

^?View Code POWERSHELL

Get-ClusterNode -Cluster ClusterName -Name Node1 | Get-ClusterGroup | Move-ClusterGroup -Name Node2 | Format-Table -Autosize;