Merge pull request #798 from mberdugo/Limitations

Considerations and limitations terminology
Zhangqi910 · Apr 10, 2024 · 239acd0 · 239acd0
2 parents 72ef95d + 31446ce
commit 239acd0
Show file tree

Hide file tree

Showing 3 changed files with 18 additions and 17 deletions.
diff --git a/docs/analysis-services/client-libraries.md b/docs/analysis-services/client-libraries.md
@@ -1,7 +1,7 @@
 ---
 title: "Analysis Services client libraries | Microsoft Docs"
 description: Download and learn how client libraries are necessary for client applications and tools to connect to Analysis Services.
-ms.date: 4/9/2024
+ms.date: 04/10/2024
 ms.service: analysis-services
 ms.custom:
 ms.topic: conceptual
@@ -17,7 +17,7 @@ monikerRange: "asallproducts-allversions || azure-analysis-services-current || p
 
 Client libraries are necessary for client applications and tools to connect to Analysis Services. Microsoft client applications like Power BI Desktop, Excel, SQL Server Management Studio (SSMS), and Analysis Services projects extension for Visual Studio install all three client libraries and update them along with regular application updates. Custom client applications also require client libraries are installed. Client libraries are updated monthly. 
 
-**Important:** Before getting the latest versions, be sure to see [Known issues](#known-issues).
+**Important:** Before getting the latest versions, be sure to see [Considerations and limitations](#considerations-and-limitations).
 
 ## Download the latest
 
@@ -34,7 +34,7 @@ Client libraries are necessary for client applications and tools to connect to A
 
 Analysis Services Management Objects (AMO/TOM) and ADOMD client libraries are available as installable packages from [NuGet.org](https://www.nuget.org/). It's recommended you migrate to NuGet references instead of using Windows Installer.
 
-Starting Feb. 2021, versions of [.NET Core](/dotnet/core/about) packages equivalent to the AMO and ADOMD client packages are also available. There are, however, a few scenarios not-supported by the .NET Core versions. To learn more, see [Known issues](#known-issues) later in this article.
+Starting Feb. 2021, versions of [.NET Core](/dotnet/core/about) packages equivalent to the AMO and ADOMD client packages are also available. There are, however, a few scenarios not-supported by the .NET Core versions. To learn more, see [considerations and limitations](#considerations-and-limitations) later in this article.
 
 NuGet package assemblies AssemblyVersion follow semantic versioning: MAJOR.MINOR.PATCH. NuGet references load the expected version even if there's a different version in the GAC (resulting from MSI install). PATCH is incremented for each release. AMO and ADOMD versions are kept in-sync.
 
@@ -76,7 +76,7 @@ To minimize risk and potential security vulnerabilities, beginning June 30, 2021
 |AMO     |   15.1.61.21        |    19.12.3.0      |
 |ADOMD     |   15.1.61.21        |    19.12.3.0      |
 
-## Known issues
+## Considerations and limitations
 
 #### AMO and ADOMD
 

diff --git a/docs/analysis-services/instances/encryption-upgrade.md b/docs/analysis-services/instances/encryption-upgrade.md
@@ -25,7 +25,7 @@ For tabular model databases at the 1600 and higher compatibility level, the foll
 
 "**New Tabular database '%{DatabaseName/}' is not using latest encryption schema. Please run RemoveDiscontinuedFeatured command with EnsureProperEncryption option (or restore DB from backup file with the same option) to upgrade to the latest encryption.**"
 
-To upgrade encryption, either backup the database and then restore with the **EnsureProperEncryption** option enabled by running the following XMLA command in SQL Server Management Studio:
+To upgrade encryption, either back up the database and then restore with the **EnsureProperEncryption** option enabled by running the following XMLA command in SQL Server Management Studio:
 
 ```xml
 <Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine" Transaction="false" xmlns:ddl100_100="http://schemas.microsoft.com/analysisservices/2008/engine/100/100" xmlns:ddl100="http://schemas.microsoft.com/analysisservices/2008/engine/100">
@@ -37,7 +37,7 @@ To upgrade encryption, either backup the database and then restore with the **En
 </Batch>
 ```
 
-or if the database is already loaded, run the following XMLA command in SQL Server Management Studio:
+Or, if the database is already loaded, run the following XMLA command in SQL Server Management Studio:
 
 ```xml
 <RemoveDiscontinuedFeatures xmlns='http://schemas.microsoft.com/analysisservices/2003/engine' xmlns:ddl922='http://schemas.microsoft.com/analysisservices/2022/engine/922'>
@@ -53,9 +53,9 @@ For multidimensional model databases at all compatibility levels, the following
 
 "**Multi-dimensional database '%{DatabaseName/}' is not using latest encryption schema. Please create a backup file and restore DB from backup file with the option EnsureProperEncryption to upgrade to the latest encryption.**"
 
-To upgrade encryption, backup the database and then restore with the **EnsureProperEncryption** option enabled.
+To upgrade encryption, back up the database and then restore with the **EnsureProperEncryption** option enabled.
 
-or if the database is already loaded, run the following XMLA command in SQL Server Management Studio:
+Or, if the database is already loaded, run the following XMLA command in SQL Server Management Studio:
 
 ```xml
 <RemoveDiscontinuedFeatures xmlns='http://schemas.microsoft.com/analysisservices/2003/engine' xmlns:ddl922='http://schemas.microsoft.com/analysisservices/2022/engine/922'>
@@ -64,29 +64,30 @@ or if the database is already loaded, run the following XMLA command in SQL Serv
 </RemoveDiscontinuedFeatures>
 
 ```
+
 ## Analysis Services service account change procedure limitations after installing SQL Server 2022 CU1
 
-Changing service accounts directly is not supported because of the new design.
+Changing service accounts directly isn't supported because of the new design.
 
 Beginning with SQL Server 2022 CU1, Analysis Services server encrypts secret artifacts, such as database connection strings, by using an encryption key that is protected per identity of the service account.
- 
+
 If you require the transfer of databases between services operating under different accounts, it's essential to follow the backup and restore method. This approach ensures a more seamless transition between service accounts while preserving the integrity of your data.
- 
-1. Use SSMS to backup each database into .abf file.
+
+1. Use SSMS to back up each database into .abf file.
 
 2. Stop SSAS service.
 
 3. Change the SSAS service account.
 
-4. Delete the content of the Data folder, except the administrators.n.xml file and master.vmp file .
+4. Delete the content of the Data folder, except the administrators.n.xml file and master.vmp file.
 
 5. Start SSAS service.
 
 6. Restore the databases from the backup .abf files.
 
 Use caution when implementing these steps to avoid data loss or security vulnerabilities. Always perform data backups and seek guidance from your system administrator prior to making substantial changes to service accounts or server configurations.
 
-## Known issues
+## Troubleshooting
 
 **Problem:** If the backup/restore steps above aren't followed, changing SQL Server 2022 Analysis Services service account can cause the service to fail to start.
 
@@ -105,5 +106,5 @@ The following encrypted properties must then be configured by using SQL Server M
 
 ## See also
 
-[Backup and restore Analysis Services Databases](../multidimensional-models/backup-and-restore-of-analysis-services-databases.md)  
+[Back up and restore Analysis Services Databases](../multidimensional-models/backup-and-restore-of-analysis-services-databases.md)  
 [Compatibility level for tabular models](../tabular-models/compatibility-level-for-tabular-models-in-analysis-services.md)  
diff --git a/docs/analysis-services/tom/table-partitions.md b/docs/analysis-services/tom/table-partitions.md
@@ -1,7 +1,7 @@
 ---
 title: "Use hot and cold table partitions to optimize very large Power BI data models"
 description: Learn how to use hot and cold table partitions to optimize very large data models in Analysis Services Management Objects (AMO) Tabular Object Model (TOM).
-ms.date: 02/06/2024
+ms.date: 04/10/2024
 ms.service: analysis-services
 ms.custom: tabular-models
 ms.topic: conceptual
@@ -138,7 +138,7 @@ As mentioned earlier, the `dataCoverageDefinition` property helps eliminate unne
 The `DataCoverageDefinition` property on *DirectQuery* partitions enables you to optimize even the largest Power BI data models based on hot partitions in import mode and cold partitions in *DirectQuery* mode by avoiding unnecessary querying of the data source.
 This source query reduction helps to boost report performance when analyzing hot data. It also helps to decrease the load on the data source, and in this way helps to maximize the scale of your data source. Yet, keep in mind that optimizing a data model by using the `dataCoverageDefinition` property is still an advanced scenario. Make sure you verify the results carefully.
 
-## Known issues and limitations
+## Considerations and limitations
 
 - Currently, the `DataCoverageDefinition` property on *DirectQuery* partitions requires static values, such as RELATED('Date'[Year]) = 2020 or RELATED('Date'[Year]) IN {2020, 2021, 2022}. Dynamic assignments are not supported, such as RELATED('Date'[DateKey]) = TODAY().