![Load SMO assembliesThe hard way :[Reflection.Assembly]::Load( ` "Microsoft.SqlServer.Smo, `Version=10.0.0.0, Culture=neutral, `PublicKeyToken=89845dcd8080cc91")# connect to SQL Server named instance# server name is L50011051# instance name is Instance1$serverName = "L50011051\Instance1"$server = New-Object –typeName ` Microsoft.SqlServer.Management.Smo.Server `-argumentList "$serverName"Is there an easier way?](https://image.slidesharecdn.com/posh4sydneyugdemo-12762527447352-phpapp01/85/Demo-for-Why-Use-PowerShell-13-320.jpg)
![Load SMO assembliesThe easier way :[System.Reflection.Assembly]::LoadWithPartialName( ` 'Microsoft.SqlServer.SMO') | out-null# This time connect to default instance# server name is L50011051# and pass in a literal$server = New-Object( ` 'Microsoft.SqlServer.Management.Smo.Server') `"L50011051" Let PowerShell do the heavy lifting with .net assemblies & reflection API](https://image.slidesharecdn.com/posh4sydneyugdemo-12762527447352-phpapp01/85/Demo-for-Why-Use-PowerShell-14-320.jpg)
![Load AMO assembliesSlightly different syntax:[Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.AnalysisServices")$as=New-Object Microsoft.AnalysisServices.Server$as.connect("L50011051")$as | Format-ListTeaser for a separate demo on PowerShell to administer Analysis Services (volunteers please…)](https://image.slidesharecdn.com/posh4sydneyugdemo-12762527447352-phpapp01/85/Demo-for-Why-Use-PowerShell-15-320.jpg)
![Other SMO assemblies#Need SmoExtended for smo.backup[System.Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.SqlServer.SmoExtended") | Out-Null[System.Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.SqlServer.ConnectionInfo") | Out-Null# 2005 specific, not available in 2008. # Use common instead[System.Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.SqlServer.SmoEnum") | Out-Nullhttp://sqlblog.com/blogs/allen_white/archive/2008/12/07/loading-smo-assemblies-into-powershell.aspx](https://image.slidesharecdn.com/posh4sydneyugdemo-12762527447352-phpapp01/85/Demo-for-Why-Use-PowerShell-16-320.jpg)
Demo for Why Use PowerShell
- 1. Why Use PowerShell(demo)Siraj Jamdar
- 2. Invoke PowerShellFrom the command line:Windows+R-> sqlpsLimited shell by design (to protect the innocent from themselves)
- 3. Invoke PowerShell from SQLContext sensitive in SSMSRight-Click -> pick Start PowerShelloptionMy favourite, pretty snappy and usefulAutomatically traverses to the correct level
- 4. Invoke PowerShell from SQLAgentSQL Agent Job StepPick PowerShell from the Type dropdown list and paste the script in the boxDreadfully slow… I’d use an SSIS package insteadUse windows scheduler, better integration with Event Viewer logsSCOM raises alerts from Event Viewer logs
- 5. Invoke PowerShellThe hard wayStart All Programs
- 6. Accessories
- 9. Invoke PowerShellTo get any real work done …runas /noprofile /user:anotherDomain\JamdarSi_adm %SystemRoot%\system32\WindowsPowerShell\ v1.0\powershell.exerunas /noprofile /user:yetanotherDomain\SJamdar%SystemRoot%\system32\WindowsPowerShell\ v1.0\powershell.exeFlex your muscles now…N.B. PowerShell 2.0 still refers to v1.0 path for backward compatibility
- 10. In real life Gotchas:Firewall is not blocking portsFirewall is not dropping packetsCorrect trust relationships are set up between AD domainsGrab the swiss ball, we’re doing Pilates now…
- 11. Check SQL SnapinsPS H:\> Get-PSSnapin -registeredName : SqlServerCmdletSnapin100PSVersion : 2.0Description : This is a PowerShell snap-in that includes various SQL Server cmdlets.Name : SqlServerProviderSnapin100PSVersion : 2.0Description : SQL Server Provider
- 12. Load SQL SnapinsAdd-PSSnapin SqlServerProviderSnapin100Add-PSSnapin SqlServerCmdletSnapin100
- 13. Load SMO assembliesThe hard way :[Reflection.Assembly]::Load( ` "Microsoft.SqlServer.Smo, `Version=10.0.0.0, Culture=neutral, `PublicKeyToken=89845dcd8080cc91")# connect to SQL Server named instance# server name is L50011051# instance name is Instance1$serverName = "L50011051\Instance1"$server = New-Object –typeName ` Microsoft.SqlServer.Management.Smo.Server `-argumentList "$serverName"Is there an easier way?
- 14. Load SMO assembliesThe easier way :[System.Reflection.Assembly]::LoadWithPartialName( ` 'Microsoft.SqlServer.SMO') | out-null# This time connect to default instance# server name is L50011051# and pass in a literal$server = New-Object( ` 'Microsoft.SqlServer.Management.Smo.Server') `"L50011051" Let PowerShell do the heavy lifting with .net assemblies & reflection API
- 15. Load AMO assembliesSlightly different syntax:[Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.AnalysisServices")$as=New-Object Microsoft.AnalysisServices.Server$as.connect("L50011051")$as | Format-ListTeaser for a separate demo on PowerShell to administer Analysis Services (volunteers please…)
- 16. Other SMO assemblies#Need SmoExtended for smo.backup[System.Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.SqlServer.SmoExtended") | Out-Null[System.Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.SqlServer.ConnectionInfo") | Out-Null# 2005 specific, not available in 2008. # Use common instead[System.Reflection.Assembly]::LoadWithPartialName( ` "Microsoft.SqlServer.SmoEnum") | Out-Nullhttp://sqlblog.com/blogs/allen_white/archive/2008/12/07/loading-smo-assemblies-into-powershell.aspx
- 17. SQL Authentication# $True for integrated security # $False for SQL authentication, meaning # supply username & password at the prompt$server.ConnectionContext.LoginSecure=$false; $credential = Get-Credential$userName = $credential.UserName –replace("\\", "")$server.ConnectionContext.set_Login($userName)$server.ConnectionContext.set_SecurePassword( ` $credential.Password)Write-Host $svr.ConnectionContext.ConnectionStringHorror story here!!!Customise sp_who$server.EnumProcesses() | `?{$_.IsSystem -eq $False -and $_.Login -eq 'sa'} | ` Select Spid, Login, Status, Cpu, MemUsage, | ` BlockingSpid, Database, Host, Command, Program | `Format-Table -auto -wrapUser spid’s onlyPick which columns to displayRe-order them, narrower columns first