Merge pull request #8890 from sevend2/UpdateSQL0508

AB#5718: update version info and remove broken link

Author: Simonx Xu

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
@@ -27,14 +27,13 @@ You might not able to connect to a named instance of Analysis Services that is i
 ## Cause
 
 The problem occurs when you start the named instance of SQL Server Analysis services (SSAS) using either SQL Server Configuration Manager or the Services applet in the Control panel.
-When you start an SSAS instance on a failover cluster using a tool other than Failover Cluster Management (Cluster administrator on older Operating Systems), that SSAS instance will run as a stand-alone instance and will listen on a non-default port resulting in connection failures from various applications.
+When you start an SSAS instance on a failover cluster using a tool other than Failover Cluster Management (Cluster administrator on older Operating Systems), that SSAS instance will run as a stand-alone instance and will listen on a nondefault port resulting in connection failures from various applications.
 
 ## Resolution
 
 Stop and restart the SQL Server Analysis services using the Failover Cluster Management tool.
 
 ## More information
 
-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.
+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 doesn't 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,27 +1,27 @@
 ---
 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
 
-Assume that you are running Microsoft SQL Server Analysis Services (SSAS) under a role for which cell security is enabled. When you try to execute an UPDATE CUBE Multidimensional Expressions (MDX) statement, the statement execution may take longer to execute than for a role for which cell security is not enabled.
+Assume that you're running Microsoft SQL Server Analysis Services (SSAS) under a role for which cell security is enabled. When you try to execute an UPDATE CUBE Multidimensional Expressions (MDX) statement, the statement execution may take longer to execute than for a role for which cell security isn't enabled.
 
 ## Cause
 
 This behavior is by design. When cell security is enabled, the Analysis Services engine executes the queries in cell-by-cell mode. If the writeback operation performs allocation at a high level, the space of leaf level cells will be large.
 
 > [!NOTE]
-> The space is not the number of rows in the fact table. The space is the full cross join space of all dimension granularity attributes. It takes a long time to enumerate those cells one-by-one in order to check the cell security.
+> The space isn't the number of rows in the fact table. The space is the full cross join space of all dimension granularity attributes. It takes a long time to enumerate those cells one-by-one in order to check the cell security.
 
 ## Workaround
 
@@ -36,7 +36,7 @@ To work around this issue, use one of the following methods.
 
 - Method 2  
 
-    Perform the writeback operation at the lowest granularity level of a certain member. You cannot allocate for many detailed granularity members.
+    Perform the writeback operation at the lowest granularity level of a certain member. You can't allocate for many detailed granularity members.
 
     > [!NOTE]
     > You may have to create dummy members in dimension tables that are marked as adjustment members in each dimension, to support the writeback operation.

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
@@ -29,9 +30,9 @@ order by count(distribtuion_key) desc
 ```
 
 > [!NOTE]
-> The `having` clause is commented out. However, if you want to perform a quick check of whether there is significant skew, this clause may tell you. You may have to adjust the having value to something that makes sense for your result set. For example, if all values have 5,000 records, we recommend that you set this value to 7,500 or 10,000 to indicate an issue.
+> The `having` clause is commented out. However, if you want to perform a quick check of whether there's significant skew, this clause may tell you. You may have to adjust the having value to something that makes sense for your result set. For example, if all values have 5,000 records, we recommend that you set this value to 7,500 or 10,000 to indicate an issue.
 
-The question of when skew becomes a problem does not have a deterministic answer. Skew becomes a problem when performance of skewed distributions becomes noticeable and the application cannot tolerate the situation. The rule of thumb is that the appliance can tolerate a skew of 10 to 20 percent across all the tables. Within this threshold, the skewed distributions should even out under concurrency. Above this threshold, you may start to see some long-running distributions when the data is processed. Some implementations may be able to tolerate greater skew, and some implementations may be unable to tolerate this much. Testing is required to determine the actual threshold for your implementation.
+The question of when skew becomes a problem doesn't have a deterministic answer. Skew becomes a problem when performance of skewed distributions becomes noticeable and the application can't tolerate the situation. The rule of thumb is that the appliance can tolerate a skew of 10 to 20 percent across all the tables. Within this threshold, the skewed distributions should even out under concurrency. Above this threshold, you may start to see some long-running distributions when the data is processed. Some implementations may be able to tolerate greater skew, and some implementations may be unable to tolerate this much. Testing is required to determine the actual threshold for your implementation.
 
 ## More information
 

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,24 +1,23 @@
 ---
 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 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 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 don't specify a location to save the error output.
 - You execute the SSIS package.
 
 In this scenario, the following error message is logged in the SSIS log:
@@ -31,19 +30,19 @@ at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSMana
 
 ## Cause
 
-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.
+This problem occurs because a destination isn't set for the error output that is generated for rows that don't 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
 
-  If you do not want to redirect error rows, follow these steps to resolve the issue:
+  If you don't want to redirect error rows, follow these steps to resolve the issue:
 
   1. Open the DQS Component in the DQS Cleansing Transformation Editor.  
   1. Select Fail Component in the Configure error output drop-down list at the bottom of the DQS Cleansing Transformation Editor.
 
 - Method 2
 
-  If you have to redirect your error rows, then you must make sure that you have a destination location for the errors to be redirected to.
+  If you have to redirect your error rows, you must make sure that you have a destination location for the errors to be redirected to.

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