Skip to content

Commit 70ec52f

Browse files
authored
Merge pull request #17203 from DCtheGeek/dmc-links-databaseengine-1
Links: SQL - database-engine - 1
2 parents 1509adc + e7291a7 commit 70ec52f

50 files changed

Lines changed: 127 additions & 180 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

docs/database-engine/availability-groups/windows/perform-a-forced-manual-failover-of-an-availability-group-sql-server.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -172,13 +172,13 @@ ms.author: mathoma
172172
```
173173
174174
> [!NOTE]
175-
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] PowerShell environment. For more information, see [Get Help SQL Server PowerShell](../../../relational-databases/scripting/get-help-sql-server-powershell.md).
175+
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] PowerShell environment. For more information, see [Get Help SQL Server PowerShell](../../../powershell/sql-server-powershell.md).
176176
177177
3. After forcing an availability group to fail over, complete the necessary follow-up steps. For more information, see [Follow Up: Essential Tasks After a Forced Failover](#FollowUp), later in this topic.
178178
179179
**To set up and use the SQL Server PowerShell provider**
180180
181-
- [SQL Server PowerShell Provider](../../../relational-databases/scripting/sql-server-powershell-provider.md)
181+
- [SQL Server PowerShell Provider](../../../powershell/sql-server-powershell-provider.md)
182182
183183
## <a name="FollowUp"></a> Follow Up: Essential Tasks After a Forced Failover
184184
@@ -312,13 +312,13 @@ ms.author: mathoma
312312
313313
- **Blogs:**
314314
315-
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)
315+
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](/archive/blogs/sqlalwayson/)
316316
317-
[CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)
317+
[CSS SQL Server Engineers Blogs](/archive/blogs/psssql/)
318318
319319
- **Whitepapers:**
320320
321-
[Microsoft SQL Server Always On Solutions Guide for High Availability and Disaster Recovery](https://go.microsoft.com/fwlink/?LinkId=227600)
321+
[Microsoft SQL Server Always On Solutions Guide for High Availability and Disaster Recovery](/previous-versions/sql/sql-server-2012/hh781257(v=msdn.10))
322322
323323
[Microsoft White Papers for SQL Server 2012](https://social.technet.microsoft.com/wiki/contents/articles/13146.white-paper-gallery-for-sql-server.aspx#[Category]SQLServer2012)
324324
@@ -332,4 +332,3 @@ ms.author: mathoma
332332
[Monitoring of Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/monitoring-of-availability-groups-sql-server.md)
333333
[Windows Server Failover Clustering &#40;WSFC&#41; with SQL Server](../../../sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server.md)
334334
335-

docs/database-engine/availability-groups/windows/perform-a-planned-manual-failover-of-an-availability-group-sql-server.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ A planned manual failover is supported only when the primary replica and the tar
8989
2. Use the **Switch-SqlAvailabilityGroup** cmdlet.
9090
9191
> [!NOTE]
92-
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)] PowerShell environment. For more information, see [Get help for SQL Server PowerShell](../../../relational-databases/scripting/get-help-sql-server-powershell.md).
92+
> To view the syntax of a cmdlet, use the **Get-Help** cmdlet in the [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)] PowerShell environment. For more information, see [Get help for SQL Server PowerShell](../../../powershell/sql-server-powershell.md).
9393
9494
The following example manually fails over the *MyAg* availability group to the secondary replica with the specified path:
9595
@@ -99,8 +99,8 @@ A planned manual failover is supported only when the primary replica and the tar
9999
100100
To set up and use the SQL Server PowerShell provider:
101101
102-
- [SQL Server PowerShell provider](../../../relational-databases/scripting/sql-server-powershell-provider.md)
103-
- [Get help for SQL Server PowerShell](../../../relational-databases/scripting/get-help-sql-server-powershell.md)
102+
- [SQL Server PowerShell provider](../../../powershell/sql-server-powershell-provider.md)
103+
- [Get help for SQL Server PowerShell](../../../powershell/sql-server-powershell.md)
104104
105105
## <a name="FollowUp"></a> Follow up: After you manually fail over an availability group
106106
If you failed over outside the [!INCLUDE[ssFosAuto](../../../includes/ssfosauto-md.md)] of the availability group, adjust the quorum votes of the Windows Server failover clustering nodes to reflect your new availability group configuration. For more information, see [Windows Server failover clustering &#40;WSFC&#41; with SQL Server](../../../sql-server/failover-clusters/windows/windows-server-failover-clustering-wsfc-with-sql-server.md).
@@ -117,4 +117,3 @@ A planned manual failover is supported only when the primary replica and the tar
117117
* [Failover and failover modes &#40;AlwaysOn availability groups&#41;](../../../database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md)
118118
* [Perform a forced manual failover of an availability group &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/perform-a-forced-manual-failover-of-an-availability-group-sql-server.md)
119119
120-

docs/database-engine/availability-groups/windows/prereqs-migrating-log-shipping-to-always-on-availability-groups.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ ms.author: mathoma
5353

5454
**For more information:**
5555

56-
[Converting a log shipping configuration to Availability Group](https://blogs.msdn.microsoft.com/sqlalwayson/2012/01/09/converting-a-logshipping-configuration-to-availability-group/) (a SQL Server blog)
56+
[Converting a log shipping configuration to Availability Group](/archive/blogs/sqlalwayson/converting-a-logshipping-configuration-to-availability-group) (a SQL Server blog)
5757

5858
## <a name="RelatedTasks"></a> Related Tasks
5959
**Log shipping**
@@ -80,17 +80,17 @@ ms.author: mathoma
8080

8181
- **Blogs:**
8282

83-
[Converting a logshipping configuration to Availability Group](https://blogs.msdn.microsoft.com/sqlalwayson/2012/01/09/converting-a-logshipping-configuration-to-availability-group/)
83+
[Converting a logshipping configuration to Availability Group](/archive/blogs/sqlalwayson/converting-a-logshipping-configuration-to-availability-group)
8484

85-
[Add a Log Shipping Primary Database and Secondary Database(s) to an Existing Availability Group](https://blogs.msdn.microsoft.com/sqlalwayson/2012/02/01/add-a-log-shipping-primary-database-and-secondary-databases-to-an-existing-availability-group/)
85+
[Add a Log Shipping Primary Database and Secondary Database(s) to an Existing Availability Group](/archive/blogs/sqlalwayson/add-a-log-shipping-primary-database-and-secondary-databases-to-an-existing-availability-group)
8686

87-
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)
87+
[SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](/archive/blogs/sqlalwayson/)
8888

89-
[CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)
89+
[CSS SQL Server Engineers Blogs](/archive/blogs/psssql/)
9090

9191
- **Whitepapers:**
9292

93-
[Migration Guide: Migrating to Always On Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping](https://msdn.microsoft.com/library/jj635217)
93+
[Migration Guide: Migrating to Always On Availability Groups from Prior Deployments Combining Database Mirroring and Log Shipping](/previous-versions/sql/sql-server-2012/jj635217(v=msdn.10))
9494

9595
[Microsoft White Papers for SQL Server 2012](https://social.technet.microsoft.com/wiki/contents/articles/13146.white-paper-gallery-for-sql-server.aspx#[Category]SQLServer2012)
9696

@@ -101,4 +101,3 @@ ms.author: mathoma
101101
[Overview of Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
102102
[Monitoring of Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/monitoring-of-availability-groups-sql-server.md)
103103

104-

0 commit comments

Comments
 (0)