Update powershell-extension.md

Author: SQLvariant

docs/azure-data-studio/powershell-extension.md

@@ -57,7 +57,7 @@ Read the [FAQ](https://github.com/PowerShell/vscode-powershell/wiki/FAQ) for ans
 
 ## Installing PowerShell Core
 
-If you are running Azure Data Studio on macOS or Linux, you may also need to install PowerShell Core.
+If you are running Azure Data Studio on MacOS or Linux, you may also need to install PowerShell Core.
 
 PowerShell Core is an Open Source project on [GitHub](https://github.com/powershell/powershell).
 For more information on installing PowerShell Core on MacOS or Linux platforms, see the following articles:
@@ -83,45 +83,13 @@ or if you're using the preview version of the extension
 $HOME/.azuredatastudio/extensions/ms-vscode.powershell-preview-<version>/examples
 ```
 
-To open/view the extension's examples in Azure Data Studio, run the following code from your PowerShell command prompt:
+To open/view the extension's examples in Azure Data Studio, run the following from your PowerShell command prompt:
 
 ```powershell
 azuredatastudio (Get-ChildItem $Home\.azuredatastudio\extensions\ms-vscode.PowerShell-*\examples)[-1]
 ```
 
-### Creating and opening files
-
-To create and open a new file inside the editor, use the New-EditorFile from within the PowerShell Integrated Terminal.
-
-```powershell
-PS C:\temp> New-EditorFile ExportData.ps1
-```
-
-This command works for any file type, not just PowerShell files.
-
-```powershell
-PS C:\temp> New-EditorFile ImportData.py
-```
-
-To open one or more files in Azure Data Studio, use the `Open-EditorFile` command.
-
-```powershell
-Open-EditorFile ExportData.ps1, ImportData.py
-```
-
-### No focus on console when executing
-
-For those users who are used to working with SSMS, you're used to being able to execute a query, and then being able to re-execute it again without having to switch back to the query pane.  In this case, the default behavior of the code editor may feel strange to you.  To keep the focus in the editor when you execute with <kbd>F8</kbd> change the following setting:
-
-```json
-"powershell.integratedConsole.focusConsoleOnExecute": false
-```
-
-The default is `true` for accessibility purposes.
-
-Be aware this setting will prevent the focus from changing to the console, even when you use a command that explicitly calls for input, like `Get-Credential`.
-
-## SQL PowerShell Examples
+### SQL PowerShell Examples
 In order to use these examples (below), you need to install the SqlServer module from the [PowerShell Gallery](https://www.powershellgallery.com/packages/SqlServer).
 
 ```powershell
@@ -145,34 +113,17 @@ Instance Name             Version    ProductLevel UpdateLevel  HostPlatform Host
 ServerA                   13.0.5233  SP2          CU4          Windows      Windows Server 2016 Datacenter
 ServerB                   14.0.3045  RTM          CU12         Linux        Ubuntu
 ```
-The `SqlServer` module contains a Provider called `SQLRegistration` which allows you to programmatically access the following types of saved SQL Server connections:
-
-+ Database Engine Server (Registered Servers)
-+ Central Management Server (CMS)
-+ Analysis Services
-+ Integration Services
-+ Reporting Services
-
-In the following example, we will do a `dir` (alias for `Get-ChildItem`) to get the list of all SQL Server instances listed in your Registered Servers file.
-
-```powershell
-dir 'SQLSERVER:\SQLRegistration\Database Engine Server Group' -Recurse 
-```
 
-Here is a sample of what that output could look like:
+In the following example, we will do a `dir` (alias for `Get-ChildItem`) to get the list of all SQL Server instances listed in your Registered Servers file, and then use the `Get-SqlDatabase` cmdlet to get a list of Databases for each of those instances.
 
 ```powershell
-Mode Name
----- ----
--    ServerA
--    ServerB
--    localhost\SQL2017
--    localhost\SQL2016Happy
--    localhost\SQL2017
+dir 'SQLSERVER:\SQLRegistration\Database Engine Server Group' -Recurse |
+WHERE { $_.Mode -ne 'd' } |
+FOREACH {
+    Get-SqlDatabase -ServerInstance $_.Name
+}
 ```
 
-For many operations that involve a database, or objects within a database, the `Get-SqlDatabase` cmdlet can be used.  If you supply values for both the `-ServerInstance` and `-Database` parameters, only that one database object will be retrieved.  However, if you specify only the `-ServerInstance` parameter, a full list of all databases on that instance will be returned.
-
 Here is a sample of what that output will look like:
 
 ```
@@ -190,7 +141,7 @@ tempdb               Normal       72.00 MB   61.25 MB Simple       140 sa
 WideWorldImporters   Normal         3.2 GB     2.6 GB Simple       130 sa
 ```
 
-This next example uses the `Get-SqlDatabase` cmdlet to retrieve a list of all databases on the ServerB instance, then presents a grid/table (using the `Out-GridView` cmdlet) to select which databases should be backed up.  Once the user clicks on the "OK" button, only the highlighted databases will be backed up.
+This example uses the `Get-SqlDatabase` cmdlet to retrieve a list of all databases on the ServerB instance, then presents a grid/table (using the `Out-GridView` cmdlet) to select which databases should be backed up.  Once the user clicks on the "OK" button, only the highlighted databases will be backed up.
 
 ```powershell
 Get-SqlDatabase -ServerInstance ServerB |
@@ -208,6 +159,28 @@ FOREACH {
 }
 ```
 
+### SQL PowerShell Examples
+In order to use these examples (below), you need to install the SqlServer module from the [PowerShell Gallery](https://www.powershellgallery.com/packages/SqlServer).
+
+```powershell
+Install-Module -Name SqlServer -AllowPrerelease
+```
+
+In this example, we use the `Get-SqlInstance` cmdlet to Get the Server SMO objects for ServerA & ServerB.  The default output for this command will include the Instance name, version, Service Pack, & CU Update Level of the instances.
+
+```powershell
+Get-SqlInstance -ServerInstance ServerA, ServerB
+```
+
+Here is a sample of what that output will look like:
+
+```
+Instance Name             Version    ProductLevel UpdateLevel
+-------------             -------    ------------ -----------
+ServerA                   13.0.5233  SP2          CU4
+ServerB                   14.0.3045  RTM          CU12
+```
+
 In this example, we will do a `dir` (alias for `Get-ChildItem`) to get the list of all SQL Server instances listed in your Registered Servers file, and then use the `Get-SqlDatabase` cmdlet to get a list of Databases for each of those instances.
 
 ```powershell
@@ -235,6 +208,24 @@ tempdb               Normal       72.00 MB   61.25 MB Simple       140 sa
 WideWorldImporters   Normal         3.2 GB     2.6 GB Simple       130 sa   
 ```
 
+This example uses the `Get-SqlDatabase` cmdlet to retrieve a list of all databases on the ServerB instance, then presents a grid/table (using the `Out-GridView` cmdlet) to select which databases should be backed up.  Once the user clicks on the "OK" button, only the highlighted databases will be backed up.
+
+```powershell
+Get-SqlDatabase -ServerInstance ServerB |
+Out-GridView -PassThru |
+Backup-SqlDatabase -CompressionOption On
+```
+
+This example, again, gets a list of all SQL Server instances listed in your Registered Servers file, then calls the `Get-SqlAgentJobHistory` which reports every failed SQL Agent Job since Midnight, for each SQL Server instance listed.
+
+```powershell
+dir 'SQLSERVER:\SQLRegistration\Database Engine Server Group' -Recurse |
+WHERE {$_.Mode -ne 'd' } |
+FOREACH {
+    Get-SqlAgentJobHistory -ServerInstance  $_.Name -Since Midnight -OutcomesType Failed
+}
+```
+
 ## Reporting Problems
 
 If you experience any problems with the PowerShell Extension, see