Merge pull request #196 from MicrosoftDocs/main638927065234170260sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/analysis-services/globalization-tips-and-best-practices-analysis-services.md

@@ -123,7 +123,7 @@ These tips and guidelines can help increase the portability of your multidimensi
 
 3. **Use ISO date formats for universal date and time information**  
 
-     One [Analysis Services expert](http://geekswithblogs.net/darrengosbell/Default.aspx) has this recommendation: "I always use the ISO date format yyyy-mm-dd for any date strings that I pass in to queries in SQL or MDX because it's unambiguous and will work regardless of the client or server's regional settings. I would agree that the server should defer to its regional settings when parsing an ambiguous date format, but I also think that if you've got an option that is not open to interpretation that you are better choosing that anyway".  
+     One [Analysis Services expert](https://darren.gosbell.com/) has this recommendation: "I always use the ISO date format yyyy-mm-dd for any date strings that I pass in to queries in SQL or MDX because it's unambiguous and will work regardless of the client or server's regional settings. I would agree that the server should defer to its regional settings when parsing an ambiguous date format, but I also think that if you've got an option that is not open to interpretation that you are better choosing that anyway".  
 
 4. **Use the Format function to enforce a specific format, regardless of regional language settings**  
 

docs/analysis-services/index.yml

@@ -63,7 +63,7 @@ landingContent:
           - text: Install SQL Server Analysis Services
             url: instances/install-windows/install-analysis-services.md
           - text: Install SQL Server evaluation editions
-            url: https://www.microsoft.com/evalcenter/evaluate-sql-server-2019-rc/
+            url: https://www.microsoft.com/evalcenter/evaluate-sql-server-2019/
           - text: SQL Server 2014 Analysis Services
             url: /previous-versions/sql/2014/analysis-services/analysis-services?preserve-view=true&view=sql-server-2014
 

docs/analysis-services/instances/configure-service-accounts-analysis-services.md

@@ -137,7 +137,7 @@ All instances of Analysis Services require the **Log on as a service** (SeServic
 |DirectQuery|Create a database login for the service account|DirectQuery is a tabular feature used to query external datasets that are either too large to fit inside the tabular model or have other characteristics that make DirectQuery a better fit than the default in-memory storage option. One of the connection options available in DirectQuery mode is to use the service account. Once again, this option works only when the service account has a database login and read permissions on the target data source. See [Set Impersonation Options (SSAS - Multidimensional)](../../analysis-services/multidimensional-models/set-impersonation-options-ssas-multidimensional.md) for more information about how the service account option is used for this task. Alternatively, the credentials of the current user can be used to retrieve data. In most cases this option entails a double-hop connection, so be sure to configure the service account for Kerberos constrained delegation so that the service account can delegate identities to a downstream server. For more information, see [Configure Analysis Services for Kerberos constrained delegation](../../analysis-services/instances/configure-analysis-services-for-kerberos-constrained-delegation.md).|  
 |Remote access to other SSAS instances|Add the service account to Analysis Services database roles defined on the remote server|Remote partitions and referencing linked objects on other remote [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] instances are both system capabilities requiring permissions on a remote computer or device. When a person creates and populates remote partitions, or sets up a linked object, that operation runs in the security context of the current user. If you subsequently automate these operations, [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] will access remote instances in the security context of its service account. In order to access linked objects on a remote instance of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)], the logon account must have permission to read the appropriate objects on the remote instance, such as Read access to certain dimensions. Similarly, using remote partitions requires that the service account have administrative rights on the remote instance. Such permissions are granted on the remote Analysis Services instance, using roles that associate permitted operations with a specific object. See [Grant database permissions (Analysis Services)](../../analysis-services/multidimensional-models/grant-database-permissions-analysis-services.md) for instructions on how to grant Full Control permissions that allow processing and query operations. See [Create and Manage a Remote Partition (Analysis Services)](../../analysis-services/multidimensional-models/create-and-manage-a-remote-partition-analysis-services.md) for more information about remote partitions.|  
 |Writeback|Add the service account to Analysis Services database roles defined on the remote server|When enabled in client applications, writeback is a feature of multidimensional models that allows the creation of new data values during data analysis. If writeback is enabled within any dimension or cube, the [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] service account must have write permissions to the writeback table in the source [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] relational database. If this table does not already exist and needs to be created, the [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] service account must also have create table permissions within the designated [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database.|  
-|Write to a query log table in a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] relational database|Create a database login for the service account and assign write permissions on the query log table|You can enable query logging to collect usage data in a database table for subsequent analysis. The [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] service account must have write permissions to the query log table in the designated [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database. If this table does not already exist and needs to be created, the [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] logon account must also have create table permissions within the designated [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database. For more information, see [Improve SQL Server Analysis Services Performance with the Usage Based Optimization Wizard (Blog)](https://www.mssqltips.com/sqlservertip/2876/improve-sql-server-analysis-services-performance-with-the-usage-based-optimization-wizard/) and [Query Logging in Analysis Services (Blog)](https://weblogs.asp.net/miked/archive/2013/07/31/query-logging-in-analysis-services.aspx).|  
+|Write to a query log table in a [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] relational database|Create a database login for the service account and assign write permissions on the query log table|You can enable query logging to collect usage data in a database table for subsequent analysis. The [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] service account must have write permissions to the query log table in the designated [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database. If this table does not already exist and needs to be created, the [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] logon account must also have create table permissions within the designated [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] database. For more information, see [Improve SQL Server Analysis Services Performance with the Usage Based Optimization Wizard (Blog)](https://www.mssqltips.com/sqlservertip/2876/improve-sql-server-analysis-services-performance-with-the-usage-based-optimization-wizard/).|  
 
 ## Related content 
  [Configure Windows Service Accounts and Permissions](/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions)   

docs/analysis-services/multidimensional-models/blog-analysis-services-cube-processing-fails-with-error.md

@@ -248,7 +248,7 @@ For more information on the architecture of cube processing, see [Analysis Servi
 
 ## Aggregation memory impact on timeouts
 
-There's an advanced setting of **AggregationMemoryLimitMax**. For more information, see [this blog post](http://geekswithblogs.net/ManicArchitect/archive/2010/11/02/142558.aspx)
+There's an advanced setting of **AggregationMemoryLimitMax**.
 
 SQL Server Analysis Services uses memory quota to control the number of concurrent jobs. Each job calculates how much memory it needs to finish the job and requests the memory quota based on its estimate. The job proceeds only when the memory quota is granted. We estimate the quota for an aggregation job. The configuration settings that control the memory usage estimates are **AggregationMemoryLimitMin** and **AggregationMemoryLimitMax**.
 
@@ -281,4 +281,4 @@ After the user removed the special characters, processing worked as expected.
 
 You might be able to further isolate the error to a specific partition. If you partitioned your cube, there might be a poorly performing query under one of the partitions.
 
-Experiment with the partition query. Change from a direct **Named Query Table** in the **Data Source** view to an underlying SQL query instead.
+Experiment with the partition query. Change from a direct **Named Query Table** in the **Data Source** view to an underlying SQL query instead.