Broken link fix

Author: v-surgos

docs/analytics-platform-system/install-the-scom-management-packs.md

@@ -24,7 +24,7 @@ For the APS PDW workload, download the [System Center Management Pack for the Mi
 
 For the appliance management, download the [SQL Server Appliance Base Management Pack](/previous-versions/system-center/packs/gg602398(v=technet.10)).  
 
-For older versions of PDW without APS, download the[System Center Monitoring Pack for Microsoft SQL Server 2012 Parallel Data Warehouse Appliance](https://go.microsoft.com/fwlink/p/?LinkId=282661).  
+For older versions of PDW without APS, download the[System Center Monitoring Pack for Microsoft SQL Server 2012 Parallel Data Warehouse Appliance](https://docs.microsoft.com/sql/analytics-platform-system/download-and-apply-microsoft-updates?view=aps-pdw-2016-au7).  
 
 <!-- MISSING LINKS - For the HDInsight workload, download the [System Center Management Pack for HDInsight](https://go.microsoft.com/fwlink/?LinkId=390208).  -->
 

docs/connect/jdbc/reference/getclientconnectionid-method-sqlserverconnection.md

@@ -53,7 +53,7 @@ UUID conid = ((ISQLServerConnection)cn).getClientConnectionId();
 
  **getClientConnectionID** works regardless of which version of the server you connect to, but extended events logs and entry on connectivity ring buffer errors will not be present in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] 2008 R2 and earlier.  
 
- You can locate the connection ID in the extended events log to see if the failure was on the server if the extended event for logging connection ID is enabled. You can also locate the connection ID in the connection ring buffer ([Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer](https://go.microsoft.com/fwlink/?LinkId=207752)) for certain connection errors. If the connection ID is not in the connection ring buffer, you can assume a network error.  
+ You can locate the connection ID in the extended events log to see if the failure was on the server if the extended event for logging connection ID is enabled. You can also locate the connection ID in the connection ring buffer ([Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer](https://docs.microsoft.com/archive/blogs/sql_protocols/connectivity-troubleshooting-in-sql-server-2008-with-the-connectivity-ring-buffer)) for certain connection errors. If the connection ID is not in the connection ring buffer, you can assume a network error.  
 
 ## See Also  
  [SQLServerConnection Members](../../../connect/jdbc/reference/sqlserverconnection-members.md)   

docs/connect/oledb/features/accessing-diagnostic-information-in-the-extended-events-log.md

@@ -25,7 +25,7 @@ ms.author: v-daenge
 >  This feature is intended only for troubleshooting and diagnostic purposes and may not be suitable for auditing or security purposes.  
   
 ## Remarks  
- For connection operations, OLE DB Driver for SQL Server will send a client connection ID. If the connection fails, you can access the connectivity ring buffer ([Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer](https://go.microsoft.com/fwlink/?LinkId=207752)) and find the **ClientConnectionID** field and get diagnostic information about the connection failure. Client connection IDs are logged in the ring buffer only if an error occurs. (If a connection fails before sending the prelogin packet, a client connection ID will not be generated.) The client connection ID is a 16-byte GUID. You can also find the client connection ID in the extended events output target, if the **client_connection_id** action is added to events in an extended events session. You can enable data access tracing and rerun the connection command and observe the **ClientConnectionID** field in the data access trace for a failed operation, if you need further diagnostic assistance.  
+ For connection operations, OLE DB Driver for SQL Server will send a client connection ID. If the connection fails, you can access the connectivity ring buffer ([Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer](https://docs.microsoft.com/archive/blogs/sql_protocols/connectivity-troubleshooting-in-sql-server-2008-with-the-connectivity-ring-buffer)) and find the **ClientConnectionID** field and get diagnostic information about the connection failure. Client connection IDs are logged in the ring buffer only if an error occurs. (If a connection fails before sending the prelogin packet, a client connection ID will not be generated.) The client connection ID is a 16-byte GUID. You can also find the client connection ID in the extended events output target, if the **client_connection_id** action is added to events in an extended events session. You can enable data access tracing and rerun the connection command and observe the **ClientConnectionID** field in the data access trace for a failed operation, if you need further diagnostic assistance.  
 
 
  OLE DB Driver for SQL Server also sends a thread-specific activity ID. The activity ID is captured in the extended events sessions if the sessions are started with the TRACK_CAUSAILITY option enabled. For performance issues with an active connection, you can get the activity ID from the client's data access trace (**ActivityID** field) and then locate the activity ID in the extended events output. The activity ID in the extended events is a 16-byte GUID (not the same as the GUID for the client connection ID) appended with a four-byte sequence number. The sequence number represents the order of a request within a thread and indicates the relative ordering of batch and RPC statements for the thread. The **ActivityID** is optionally sent for SQL batch statements and RPC requests when data access tracing is enabled on and the 18th bit in the data access tracing configuration word is turned ON.  

docs/connect/oledb/finding-more-oledb-driver-for-sql-server-information.md

@@ -24,7 +24,7 @@ ms.author: v-daenge
  [Data Access and Storage Developer Center](https://go.microsoft.com/fwlink?linkid=4173)  
  This site provides technical articles, sample code, and other resources for OLE DB Driver for SQL Server and other data access technologies.  
 
- [Data Access Blog](https://go.microsoft.com/fwlink/?LinkId=48617)  
+ [Data Access Blog](https://techcommunity.microsoft.com/t5/sql-server/bg-p/SQLServer/label-name/SQLServerDrivers)  
  This blog site provides information about data access technologies and allows you to interact directly with members of the product team.  
 
  [Windows Data Access Components](https://go.microsoft.com/fwlink/?LinkId=107907)  

docs/data-quality-services/create-a-domain-rule.md

@@ -121,7 +121,7 @@ ms.author: sawinark
 |Value is date/time|Only values that have a SQL Server date/time data type will be valid. This includes datetime, time, date, etc.|Example operand: N/A<br /><br /> Valid values: 1916-06-04; 1916-06-04 18:24:24; March 21, 2001; 5/18/2011; 18:24:24<br /><br /> Not valid values: March 213, 2006|  
 |Value is in|Only values that are in the set in the operand will be valid.<br /><br /> To enter the values in the set, click in the operand text box, enter the first value, press Enter, enter the second value, repeat for as many values as you want to enter in the set, and then click again in the operand text box. DQS will add a comma between the values in the set. If you enter a single string with commas and no carriage return (for example, "A1, B1"), DQS will consider that string a single value in the set.|Example operand: [A1, B1]<br /><br /> Valid values: A1, B1<br /><br /> Not valid values: AA, 11|  
 |Value is not in|Only values that are not in the set in the operand will be valid.|Example operand: [A1, B1]<br /><br /> Valid values: AA, 11<br /><br /> Not valid values: A1, B1|  
-|Value matches pattern|Only values that match the pattern of characters, digits, or special characters in the operand will be valid.<br /><br /> Any letter (A...Z) can be used as a pattern for any letter; case insensitive. Any digit (0...9) can be used as a pattern for any digit. Any special character, except a letter or a digit, can be used as a pattern for itself. Brackets, [], define optional matching.|Example operand: AA:000 (a pattern of *any* two characters followed by a colon (:), which is again followed by *any* three digits.<br /><br /> Valid values: AB:012, df:257<br /><br /> Not valid values: abc:123, FJ-369<br /><br /> For more information about the pattern rules in DQS and examples, see [Pattern Matching in DQS Domain Rules](https://blogs.msdn.com/b/dqs/archive/2012/10/08/pattern-matching-in-dqs-domain-rules.aspx).|  
+|Value matches pattern|Only values that match the pattern of characters, digits, or special characters in the operand will be valid.<br /><br /> Any letter (A...Z) can be used as a pattern for any letter; case insensitive. Any digit (0...9) can be used as a pattern for any digit. Any special character, except a letter or a digit, can be used as a pattern for itself. Brackets, [], define optional matching.|Example operand: AA:000 (a pattern of *any* two characters followed by a colon (:), which is again followed by *any* three digits.<br /><br /> Valid values: AB:012, df:257<br /><br /> Not valid values: abc:123, FJ-369<br /><br /> For more information about the pattern rules in DQS and examples, see [Pattern Matching in DQS Domain Rules](https://techcommunity.microsoft.com/t5/sql-server-integration-services/pattern-matching-in-dqs-domain-rules/ba-p/388103).|  
 |Value does not match pattern|Only values that do not match the pattern of characters, digits, or special characters in the operand will be valid.|Example operand: A1 (value must not match a pattern of *any* one character followed by *any* one digit.)<br /><br /> Valid values: AB1, A, A:5<br /><br /> Not valid values: B7, c9|  
 |Value contains pattern|Only values that contain the pattern of characters, digits, or special characters in the operand will be valid.|Example operand: AA-12 (value contains a pattern of *any* two characters followed by a hyphen (-), which is again followed by *any* two digits.)<br /><br /> Valid values: AAA-01, ab-975<br /><br /> Not valid value: A7, AA-6, C-45, aa;98|  
 |Value does not contain pattern|Only values that do not contain the pattern of characters in the operand will be valid.|Example operand: AB-12 (value must not contain a pattern of *any* two characters followed by a hyphen (-), which is again followed by *any* two digits.)<br /><br /> Valid values: A7, AA-6, C-45, aa;98<br /><br /> Not valid value: AAA-01, ab-975|  

docs/database-engine/availability-groups/windows/administration-of-an-availability-group-sql-server.md

@@ -100,7 +100,7 @@ ms.author: mathoma
 -   **Blogs:**  
 
      [SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)    
-     [CSS SQL Server Engineers Blogs](https://blogs.msdn.com/b/psssql/)  
+[CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)  
 
 -   **Videos:**  
 

docs/database-engine/availability-groups/windows/always-on-availability-groups-interoperability-sql-server.md

@@ -59,7 +59,7 @@ The following features interoperate with [!INCLUDE[ssHADR](../../../includes/ssh
 
   [Migration Guide: Migrating to SQL Server 2012 Failover Clustering and Availability Groups from Prior Clustering and Mirroring Deployments](https://blogs.msdn.microsoft.com/sqlalwayson/2012/04/09/now-available-migration-guide-migrating-to-sql-server-2012-failover-clustering-and-availability-groups-from-prior-clustering-and-mirroring-deployments/)
   [SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)
-  [CSS SQL Server Engineers Blogs](https://blogs.msdn.com/b/psssql/)
+  [CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)
 
 - **Whitepapers:**
 

docs/database-engine/availability-groups/windows/always-on-availability-groups-sql-server.md

@@ -153,7 +153,7 @@ ms.author: mathoma
 
      [SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)  
 
-     [CSS SQL Server Engineers Blogs](https://blogs.msdn.com/b/psssql/)  
+     [CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)  
 
 -   **Videos:**  
 

docs/database-engine/availability-groups/windows/always-on-availability-groups-troubleshooting-and-monitoring-guide.md

@@ -67,6 +67,6 @@ ms.author: jroth
 
 ## Next steps  
  [SQL Server Always On Team Blog](https://docs.microsoft.com/archive/blogs/sqlalwayson/)   
- [CSS SQL Server Engineers Blogs](https://blogs.msdn.com/b/psssql/)  
+ [CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)  
 
 

docs/database-engine/availability-groups/windows/configuration-of-a-server-instance-for-always-on-availability-groups-sql-server.md

@@ -64,7 +64,7 @@ ms.author: mathoma
 
      [SQL Server Always On Team Blogs: The official SQL Server Always On Team Blog](https://blogs.msdn.microsoft.com/sqlalwayson/)  
 
-     [CSS SQL Server Engineers Blogs](https://blogs.msdn.com/b/psssql/)  
+     [CSS SQL Server Engineers Blogs](https://docs.microsoft.com/archive/blogs/psssql/)  
 
 -   **Videos:**