update version info and remove broken link

Author: sevend2

support/sql/analysis-services/cannot-connect-named-instance.md

@@ -1,15 +1,15 @@
 ---
 title: Can't connect to a named instance
 description: This article provides resolutions where you might not be able to connect to a named instance of Analysis Services that is installed on a failover cluster.
-ms.date: 07/22/2020
+ms.date: 05/09/2025
 ms.custom: sap:Analysis Services
-ms.reviewer: karang
+ms.reviewer: karang, gasadas
 ---
 # Cannot connect to a named instance of a clustered analysis service
 
 This article helps you resolve the problem where you might not be able to connect to a named instance of Analysis Services that is installed on a failover cluster.
 
-_Original product version:_   SQL Server 2008 R2 Enterprise, SQL Server 2008 Enterprise, Microsoft SQL Server 2005 Enterprise Edition  
+_Original product version:_   SQL Server    
 _Original KB number:_   2429685
 
 ## Symptoms
@@ -37,4 +37,3 @@ Stop and restart the SQL Server Analysis services using the Failover Cluster Man
 
 An SSAS instance started on a cluster (default or named instance) will start listening on all IP addresses of the cluster group using the default port of 2383. The server setting `<Port>` property does not change the port number of SSAS service on a cluster.
 
-For more information, see the KB article: [How to determine and change the port of an SSAS Instance](https://support.microsoft.com/help/2466860)

support/sql/analysis-services/writeback-performance-issue-cell-security-enable.md

@@ -1,15 +1,15 @@
 ---
 title: Writeback performance issue
 description: This article provides workarounds for the writeback performance problem that occurs when cell security is enabled in SQL Server Analysis Services.
-ms.date: 07/22/2020
+ms.date: 05/09/2025
 ms.custom: sap:Analysis Services
-ms.reviewer: haidongh, heidist
+ms.reviewer: haidongh, heidist, gasadas
 ---
 # Writeback performance problem when cell security is enabled in SQL Server Analysis Services
 
 This article helps you work around the writeback performance problem that occurs when cell security is enabled in SQL Server Analysis Services.
 
-_Original product version:_   SQL Server 2012 Analysis Services  
+_Original product version:_   SQL Server 2012 Analysis Services and later versions  
 _Original KB number:_   2747616
 
 ## Symptoms

support/sql/analytics-platform-system/detect-data-skew-distribution-key-values.md

@@ -1,15 +1,16 @@
 ---
 title: Detect skew on distribution key values
 description: This article describes how to detect skew on the distribution key of a distributed table in a Parallel Data Warehouse appliance.
-ms.date: 07/22/2020
+ms.date: 05/09/2025
 ms.custom: sap:Parallel Data Warehouse (APS)
 ms.topic: how-to
+ms.reviewer: jopilov, ccaldera
 ---
 # Detect data skew on the distribution key values
 
 This article shows how to detect skew on the distribution key of a distributed table in a Parallel Data Warehouse appliance.
 
-_Original product version:_   SQL Server 2008 R2 Parallel Data Warehouse  
+_Original product version:_   SQL Server Parallel Data Warehouse  
 _Original KB number:_   3046863
 
 ## Summary

support/sql/analytics-platform-system/error-cetas-to-blob-storage.md

@@ -1,15 +1,15 @@
 ---
 title: Error 105005 when you do CETAS to blob storage
 description: This article provides resolutions for the error that occurs when you do a CETAS operation to Azure Blob storage by using PolyBase.
-ms.date: 08/05/2020
+ms.date: 05/09/2025
 ms.custom: sap:Parallel Data Warehouse (APS)
-ms.reviewer: daleche, christys
+ms.reviewer: daleche, christys, ccaldera
 ---
 # Error 105005 when you do CETAS operation to Azure blob storage
 
 This article helps you resolve the problem that occurs when you do a `CREATE EXTERNAL TABLE AS SELECT (CETAS)` operation to Azure Blob storage by using PolyBase.
 
-_Original product version:_   SQL Server 2012 Parallel Data Warehouse (APS), SQL Server 2008 R2 Parallel Data Warehouse  
+_Original product version:_   SQL Server Parallel Data Warehouse (APS)   
 _Original KB number:_   3210540
 
 ## Symptoms

support/sql/data-quality-services/error-you-run-dqs-cleansing-transformation.md

@@ -1,23 +1,22 @@
 ---
 title: Error when you run the DQS Cleansing transformation
-description: This article provides two workarounds for the problem where an error is logged in the SSIS log on SQL Server 2012.
-ms.date: 01/14/2021
+description: This article provides two workarounds for the problem where an error is logged in the SSIS log on SQL Server.
+ms.date: 05/09/2025
 ms.custom: sap:Data Quality Services
-ms.reviewer: smat
-ms.topic: troubleshooting 
+ms.reviewer: smat, jopilov
 ---
-# Error (DQS Cleansing failed the pre-execute phase) when you run the DQS Cleansing transformation in SQL Server 2012
+# Error (DQS Cleansing failed the pre-execute phase) when you run the DQS Cleansing transformation in SQL Server
 
-This article helps you to work around the problem where an error is logged in the SSIS log on SQL Server 2012.
+This article helps you to work around the problem where an error is logged in the SSIS log on SQL Server.
 
-_Applies to:_   SQL Server 2012 Developer, SQL Server 2012 Enterprise, SQL Server 2012 Standard  
+_Applies to:_   SQL Server    
 _Original KB number:_   2715968
 
 ## Symptoms
 
 Consider the following scenario:
 
-- You use the Data Quality Services (DQS) Cleansing transformation in a SQL Server-Integrated Service (SSIS) Data Flow to cleanse your data in Microsoft SQL Server 2012.
+- You use the Data Quality Services (DQS) Cleansing transformation in a SQL Server-Integrated Service (SSIS) Data Flow to cleanse your data in Microsoft SQL Server.
 - You set the "Configure error output" setting of the DQS Cleansing transformation to "Redirect row." However, you do not specify a location to save the error output.
 - You execute the SSIS package.
 
@@ -33,9 +32,9 @@ at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSMana
 
 This problem occurs because a destination is not set for the error output that is generated for rows that do not meet the DQS domain criteria and rules.
 
-## Workaround
+## Resolution
 
-To resolve this issue, use one of the following methods.
+To resolve this issue, use one of the following methods:
 
 - Method 1
 

support/sql/master-data-services/mds-entity-based-staging-fail.md

@@ -1,21 +1,22 @@
 ---
 title: MDS entity-based staging may fail
-description: This article provides resolutions for the problem where MDS entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server 2012.
-ms.date: 02/22/2021
+description: This article provides resolutions for the problem where MDS entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server.
+ms.date: 05/09/2025
 ms.custom: sap:Master Data Services
+ms.reviewer: jopilov
 ---
-# MDS entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server 2012
+# MDS entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server
 
-This article helps you resolve the problem where Master Data Services (MDS) entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server 2012.
+This article helps you resolve the problem where Master Data Services (MDS) entity-based staging may fail when a duplicate Batch Tag value is used in SQL Server.
 
-_Original product version:_   SQL Server 2012  
+_Original product version:_   SQL Server    
 _Original KB number:_   2712547
 
 ## Symptoms
 
 Consider the following scenario:
 
-- You use the Microsoft SQL Server 2012 MDS entity-based staging process to import data into MDS.
+- You use the Microsoft SQL Server MDS entity-based staging process to import data into MDS.
 
 - You populate various MDS staging tables (stg.name) with the staging data by using the `BatchTag` column to identify the batch.
 
@@ -56,7 +57,7 @@ This problem occurs because the MDS entity-based staging process checks the `Bat
 
 ## Resolution
 
-If your batch is stuck in Running status, stop the batch process, and then try to process the batch again. To stop the batch process, run the SQL statement: `Exec [mdm].[udpStagingBatchQueueActivate]` To resolve this problem, update the BatchTag value in the staging table for the records to a new name. Additionally, make sure that the `importstatus_ID` field is set to *0* for the records.
+If your batch is stuck in Running status, stop the batch process, and then try to process the batch again. To stop the batch process, run the SQL statement: `Exec [mdm].[udpStagingBatchQueueActivate]`. To resolve this problem, update the BatchTag value in the staging table for the records to a new name. Additionally, make sure that the `importstatus_ID` field is set to *0* for the records.
 
 ## More information
 

support/sql/master-data-services/mds-validate-version-command-fails.md

@@ -1,21 +1,22 @@
 ---
 title: MDS Validate Version command fails
-description: This article provides resolutions for the problem where MDS Validate Version command fails with a server error in SQL Server 2012 and SQL Server 2014.
-ms.date: 02/22/2021
+description: This article provides resolutions for the problem where MDS Validate Version command fails with a server error in SQL Server.
+ms.date: 05/09/2025
 ms.custom: sap:Master Data Services
+ms.reviewer: jopilov
 ---
-# MDS Validate Version command fails with a server error in SQL Server 2012 and SQL Server 2014
+# MDS Validate Version command fails with a server error in SQL Server
 
-This article helps you resolve the problem where Master Data Services (MDS) Validate Version command fails with a server error in SQL Server 2012 and SQL Server 2014.
+This article helps you resolve the problem where Master Data Services (MDS) Validate Version command fails with a server error in SQL Server.
 
-_Original product version:_   SQL Server 2012, SQL Server 2014  
+_Original product version:_   SQL Server    
 _Original KB number:_   2711671
 
 ## Symptoms
 
 Consider the following scenario:
 
-- An administrator installs Microsoft SQL Server 2012 or SQL Server 2014 MDS and then deploys the MDS website by using a new application pool account.
+- An administrator installs Microsoft SQL Server and then deploys the MDS website by using a new application pool account.
 
 - Later, you browse to the MDS website and then follow these steps:
 

support/sql/ssms/exception-you-execute-query.md

@@ -1,15 +1,15 @@
 ---
 title: OutOfMemoryException Error When You Execute a Query
 description: This article provides workarounds for the problem that occurs when you use SQL Server Management Studio (SSMS) to run a SQL query that returns a large amount of data.
-ms.date: 04/08/2025
+ms.date: 05/09/2025
 ms.custom: sap:SQL Server Management, Query and Data Tools
 ms.reviewer: jopilov
 ---
 # OutOfMemoryException error when you execute a query in SQL Server Management Studio (SSMS)
 
 This article helps you resolve the problem that occurs when you use SQL Server Management Studio (SSMS) to run a SQL query that returns a large amount of data.
 
-_Original product version:_   SQL Server 2012, SQL Server 2008, SQL Server 2005  
+_Original product version:_   SQL Server   
 _Original KB number:_   2874903
 
 ## Symptoms