Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit ed0c0fc

Browse files
author
stevestein
committed
removed out of service versions
1 parent 95394ec commit ed0c0fc

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

docs/powershell/sql-server-powershell.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,8 @@ ms.workload: "Active"
2121
---
2222
# SQL Server PowerShell
2323
[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
24-
[!INCLUDE[ssCurrent](../includes/sscurrent-md.md)] supports Windows PowerShell.
24+
25+
**[Install SQL Server PowerShell](download-sql-server-ps-module.md)**
2526

2627
> [!NOTE]
2728
> There are two SQL Server PowerShell modules; **SqlServer** and **SQLPS**. The **SQLPS** module is included with the SQL Server installation (for backwards compatibility), but is no longer being updated. The most up-to-date PowerShell module is the **SqlServer** module. The **SqlServer** module contains updated versions of the cmdlets in **SQLPS**, and also includes new cmdlets to support the latest SQL features.
@@ -30,7 +31,7 @@ ms.workload: "Active"
3031
3132
**Why did the module change from SQLPS to SqlServer?**
3233

33-
To ship SQL PowerShell updates, we had to change the identity of the SQL PowerShell module, as well as the wrapper known as `SQLPS.exe`. Because of this change, there are now two SQL PowerShell modules, the **SQLPS** module, and the **SqlServer** module.
34+
To ship SQL PowerShell updates, we had to change the identity of the SQL PowerShell module, as well as the wrapper known as *SQLPS.exe*. Because of this change, there are now two SQL PowerShell modules, the **SqlServer** module, and the **SQLPS** module.
3435

3536
**Update your PowerShell scripts if they import the SQLPS module.**
3637

@@ -46,7 +47,8 @@ The **SqlServer** module loads two Windows PowerShell snap-ins:
4647

4748

4849
## SQL Server Versions
49-
The [!INCLUDE[ssCurrent](../includes/sscurrent-md.md)] PowerShell components can be used to manage instances of [!INCLUDE[ssVersion2000](../includes/ssversion2000-md.md)] or later. Instances of [!INCLUDE[ssVersion2005](../includes/ssversion2005-md.md)] must be running SP2 or later. Instances of [!INCLUDE[ssVersion2000](../includes/ssversion2000-md.md)] must be running SP4 or later. When the [!INCLUDE[ssCurrent](../includes/sscurrent-md.md)] PowerShell components are used with earlier versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)], they are limited to the functionality available in those versions.
50+
SQL PowerShell cmdlets can be used to manage instances of Azure SQL Database, Azure SQL Data Warehouse, and all [supported SQL Server products](https://support.microsoft.com/lifecycle/search/1044).
51+
5052

5153
## SQL Server identifiers that contain characters not supported in PowerShell paths
5254

@@ -62,4 +64,3 @@ Query expressions are strings that use syntax similar to XPath to specify a set
6264
## Cmdlet reference
6365
* [SqlServer cmdlets](https://docs.microsoft.com/powershell/module/sqlserver)
6466
* [SQLPS cmdlets](https://docs.microsoft.com/powershell/module/sqlps)
65-

0 commit comments

Comments
 (0)