Skip to content

Commit 7319da8

Browse files
MikeRayMSFTMikeRayMSFT
committed
Clean up some authorization
1 parent 680986a commit 7319da8

37 files changed

Lines changed: 60 additions & 60 deletions

File tree

‎docs/database-engine/availability-groups/windows/active-secondaries-readable-secondary-replicas-always-on-availability-groups.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ ms.author: chadam
128128
This means that there is some latency, usually only a matter of seconds, between the primary and secondary replicas. In unusual cases, however, for example if network issues reduce throughput, latency can become significant. Latency increases when I/O bottlenecks occur and when data movement is suspended. To monitor suspended data movement, you can use the [Always On Dashboard](../../../database-engine/availability-groups/windows/use-the-always-on-dashboard-sql-server-management-studio.md) or the [sys.dm_hadr_database_replica_states](../../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) dynamic management view.
129129

130130
#### <a name="bkmk_LatencyWithInMemOLTP"></a> Data Latency on databases with memory-optimized tables
131-
In [!INCLUDE[ssSQL14](../../../includes/sssql14-md.md)] there were special considerations around data latency on active secondaries - see [[!INCLUDE[ssSQL14](../../../includes/sssql14-md.md)] Active Secondaries: Readable Secondary Replicas](https://technet.microsoft.com/library/ff878253(v=sql.120).aspx). Starting [!INCLUDE[ssSQL15](../../../includes/sssql16-md.md)] there are no special considerations around data latency for memory-optimized tables. The expected data latency for memory-optimized tables is comparable to the latency for disk-based tables.
131+
In [!INCLUDE[ssSQL14](../../../includes/sssql14-md.md)] there were special considerations around data latency on active secondaries - see [[!INCLUDE[ssSQL14](../../../includes/sssql14-md.md)] Active Secondaries: Readable Secondary Replicas](https://technet.microsoft.com/library/ff878253(v=sql.120).aspx). Starting [!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)] there are no special considerations around data latency for memory-optimized tables. The expected data latency for memory-optimized tables is comparable to the latency for disk-based tables.
132132

133133
### <a name="ReadOnlyWorkloadImpact"></a> Read-Only Workload Impact
134134
When you configure a secondary replica for read-only access, your read-only workloads on the secondary databases consume system resources, such as CPU and I/O (for disk-based tables) from redo threads, especially if the read-only workloads on disk-based tables are highly I/O-intensive. There is no IO impact when accessing memory-optimized tables because all the rows reside in memory.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The following table lists [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-m
4444

4545
The following features interoperate with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] with specific restrictions. See the linked topics for details.
4646

47-
- Cross-database transactions/distributed transactions ([!INCLUDE[ssSQL15](../../../includes/sssql16-md.md)] and Windows Server 2016). For more information, see [Cross-Database Transactions and Distributed Transactions for Always On Availability Groups and Database Mirroring &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/transactions-always-on-availability-and-database-mirroring.md)
47+
- Cross-database transactions/distributed transactions ([!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)] and Windows Server 2016). For more information, see [Cross-Database Transactions and Distributed Transactions for Always On Availability Groups and Database Mirroring &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/transactions-always-on-availability-and-database-mirroring.md)
4848
- [Query statistics system data collector](../../../relational-databases/data-collection/system-data-collection-set-reports.md#Query) cannot reliably run in an environment with non-readable secondaries. To use query statistics system data collector, set all secondary availability group replicas to allow [read-access](configure-read-only-access-on-an-availability-replica-sql-server.md).
4949

5050
## <a name="NoInterop"></a> Features that Do Not Interoperate with Always On Availability Groups

‎docs/database-engine/availability-groups/windows/configure-read-only-routing-for-an-availability-group-sql-server.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ ms.author: chadam
2222
[!INCLUDE [SQL Server](../../../includes/applies-to-version/sqlserver.md)]
2323
To configure an Always On availability group to support read-only routing in [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)], you can use either [!INCLUDE[tsql](../../../includes/tsql-md.md)] or PowerShell. *Read-only routing* refers to the ability of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] to route qualifying read-only connection requests to an available Always On [readable secondary replica](../../../database-engine/availability-groups/windows/active-secondaries-readable-secondary-replicas-always-on-availability-groups.md) (that is, a replica that is configured to allow read-only workloads when running under the secondary role). To support read-only routing, the availability group must possess an [availability group listener](../../../database-engine/availability-groups/windows/listeners-client-connectivity-application-failover.md). Read-only clients must direct their connection requests to this listener, and the client's connection strings must specify the application intent as "read-only." That is, they must be *read-intent connection requests*.
2424

25-
Read-only routing is available in [!INCLUDE[sssql15](../../../includes/sssql16-md.md)] and later.
25+
Read-only routing is available in [!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)] and later.
2626

2727
> [!NOTE]
2828
> For information about how to configure a readable secondary replica, see [Configure Read-Only Access on an Availability Replica &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server.md).
@@ -98,7 +98,7 @@ Read-only routing is available in [!INCLUDE[sssql15](../../../includes/sssql16-m
9898
> You must set the read-only routing URL before configuring the read-only routing list.
9999
100100
### <a name="loadbalancing"></a> Configure load-balancing across read-only replicas
101-
Beginning with [!INCLUDE[ssSQL15](../../../includes/sssql16-md.md)], you can configure load-balancing across a set of read-only replicas. Previously, read-only routing always directed traffic to the first available replica in the routing list. To take advantage of this feature, use one level of nested parentheses around the **READ_ONLY_ROUTING_LIST** server instances in the **CREATE AVAILABILITY GROUP** or **ALTER AVAILABILITY GROUP** commands.
101+
Beginning with [!INCLUDE[sssql16-md](../../../includes/sssql16-md.md)], you can configure load-balancing across a set of read-only replicas. Previously, read-only routing always directed traffic to the first available replica in the routing list. To take advantage of this feature, use one level of nested parentheses around the **READ_ONLY_ROUTING_LIST** server instances in the **CREATE AVAILABILITY GROUP** or **ALTER AVAILABILITY GROUP** commands.
102102

103103
For example, the following routing list load balances read-intent connection request across two read-only replicas, `Server1` and `Server2`. The nested parentheses that surround these servers identify the load-balanced set. If neither replica is available in that set, it will proceed to attempt to sequentially connect to the other replicas, `Server3` and `Server4`, in the read-only routing list.
104104

‎docs/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2016.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ ms.author: mikeray
2222

2323
This topic describes breaking changes in the [!INCLUDE[sssql15-md](../includes/sssql16-md.md)] [!INCLUDE[ssDE](../includes/ssde-md.md)] and earlier versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. These changes might break applications, scripts, or functionalities that are based on earlier versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. You might encounter these issues when you upgrade.
2424

25-
## <a name="SQL15"></a> Breaking Changes in [!INCLUDE[ssSQL15](../includes/sssql16-md.md)]
25+
## <a name="SQL15"></a> Breaking Changes in [!INCLUDE[sssql15-md](../includes/sssql16-md.md)]
2626

2727
- The *sample_ms* column of `sys.dm_io_virtual_file_stats` has expanded from an **int** to a **bigint** data type.
2828

‎docs/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2017.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ monikerRange: ">=sql-server-2017||>=sql-server-linux-2017"
2727
- CLR uses Code Access Security (CAS) in the .NET Framework, which is no longer supported as a security boundary. Beginning with [!INCLUDE[sssql17-md](../includes/sssql17-md.md)][!INCLUDE[ssDE](../includes/ssde-md.md)], an `sp_configure` option called `clr strict security` is introduced to enhance the security of CLR assemblies. clr strict security is enabled by default, and treats `SAFE` and `EXTERNAL_ACCESS` CLR assemblies as if they were marked `UNSAFE`. The `clr strict security` option can be disabled for backward compatibility, but this is not recommended. When `clr strict security` is disabled, a CLR assembly created with `PERMISSION_SET = SAFE` may be able to access external system resources, call unmanaged code, and acquire **sysadmin** privileges. After enabling strict security, any assemblies that are not signed will fail to load. Also, if a database has `SAFE` or `EXTERNAL_ACCESS` assemblies, `RESTORE` or `ATTACH DATABASE` statements can complete, but the assemblies may fail to load.
2828
To load the assemblies, you must either alter or drop and recreate each assembly so that it is signed with a certificate or asymmetric key that has a corresponding login with the `UNSAFE ASSEMBLY` permission on the server. For more information, see [CLR strict security](../database-engine/configure-windows/clr-strict-security.md).
2929

30-
- The MD2, MD4, MD5, SHA, and SHA1 algorithms are deprecated in [!INCLUDE[ssSQL15](../includes/sssql16-md.md)]. Up to [!INCLUDE[ssSQL15](../includes/sssql16-md.md)], a self-signed certificate is created using SHA1. Starting with [!INCLUDE[ssSQL17](../includes/sssql17-md.md)], a self-signed certificate is created using SHA2_256.
30+
- The MD2, MD4, MD5, SHA, and SHA1 algorithms are deprecated in [!INCLUDE[sssql15-md](../includes/sssql16-md.md)]. Up to [!INCLUDE[sssql15-md](../includes/sssql16-md.md)], a self-signed certificate is created using SHA1. Starting with [!INCLUDE[ssSQL17](../includes/sssql17-md.md)], a self-signed certificate is created using SHA2_256.
3131

3232
## <a name="previous-versions"></a> Previous Versions
3333

‎docs/database-engine/discontinued-database-engine-functionality-in-sql-server.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,9 @@ For current configuration options, see [ALTER DATABASE SCOPED CONFIGURATION (Tra
5555
>[!NOTE]
5656
>No features were discontinued in [!INCLUDE[sssql14](../includes/sssql17-md.md)].
5757
58-
## Discontinued features in [!INCLUDE[ssSQL15](../includes/sssql16-md.md)]
58+
## Discontinued features in [!INCLUDE[sssql15-md](../includes/sssql16-md.md)]
5959

60-
- [!INCLUDE[ssSQL15](../includes/sssql16-md.md)] is a 64-bit application. 32-bit installation is discontinued, though some elements run as 32-bit components.
60+
- [!INCLUDE[sssql15-md](../includes/sssql16-md.md)] is a 64-bit application. 32-bit installation is discontinued, though some elements run as 32-bit components.
6161

6262
- Compatibility level 90 is discontinued. For more information, see [ALTER DATABASE Compatibility Level &#40;Transact-SQL&#41;](../t-sql/statements/alter-database-transact-sql-compatibility-level.md).
6363

‎docs/database-engine/install-windows/validate-a-sql-server-installation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ monikerRange: ">=sql-server-2016"
1818

1919
[!INCLUDE [SQL Server -Windows Only](../../includes/applies-to-version/sql-windows-only.md)]
2020

21-
The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] discovery report can be used to verify the version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features installed on the computer. The **Installed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report** displays a report of all [!INCLUDE[ssVersion2000](../../includes/ssversion2000-md.md)], [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], and [!INCLUDE[ssSQL15](../../includes/sssql17-md.md)] products and features that are installed on the local server. The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report is available on the **Tools** page on the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Installation center.
21+
The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] discovery report can be used to verify the version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features installed on the computer. The **Installed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report** displays a report of all [!INCLUDE[ssVersion2000](../../includes/ssversion2000-md.md)], [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)], [!INCLUDE[ssKatmai](../../includes/sskatmai-md.md)], [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)], [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], and [!INCLUDE[sssql17-md](../../includes/sssql17-md.md)] products and features that are installed on the local server. The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report is available on the **Tools** page on the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Installation center.
2222

2323
## Run [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report
2424

‎docs/includes/alter-workload-group.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ ALTER WORKLOAD GROUP { group_name | "default" }
7272
> By default, Resource Governor will not prevent a request from continuing if the maximum time is exceeded. However, an event will be generated. For more information, see [CPU Threshold Exceeded Event Class](../relational-databases/event-classes/cpu-threshold-exceeded-event-class.md).
7373
7474
> [!IMPORTANT]
75-
> Starting with [!INCLUDE[ssSQL15](sssql16-md.md)] SP2 and [!INCLUDE[ssSQL17](sssql17-md.md)] CU3, and using [trace flag 2422](../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md), Resource Governor will abort a request when the maximum time is exceeded.
75+
> Starting with [!INCLUDE[sssql16-md](sssql16-md.md)] SP2 and [!INCLUDE[ssSQL17](sssql17-md.md)] CU3, and using [trace flag 2422](../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md), Resource Governor will abort a request when the maximum time is exceeded.
7676
7777
REQUEST_MEMORY_GRANT_TIMEOUT_SEC =*value*
7878
Specifies the maximum time, in seconds, that a query can wait for memory grant (work buffer memory) to become available.

‎docs/includes/create-workload-group.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Specifies the maximum amount of CPU time, in seconds, that a request can use. *v
6464
> [!NOTE]
6565
> By default, Resource Governor will not prevent a request from continuing if the maximum time is exceeded. However, an event will be generated. For more information, see [CPU Threshold Exceeded Event Class](../relational-databases/event-classes/cpu-threshold-exceeded-event-class.md).
6666
> [!IMPORTANT]
67-
> Starting with [!INCLUDE[ssSQL15](sssql16-md.md)] SP2 and [!INCLUDE[ssSQL17](sssql17-md.md)] CU3, and using [trace flag 2422](../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md), Resource Governor will abort a request when the maximum time is exceeded.
67+
> Starting with [!INCLUDE[sssql16-md](sssql16-md.md)] SP2 and [!INCLUDE[ssSQL17](sssql17-md.md)] CU3, and using [trace flag 2422](../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md), Resource Governor will abort a request when the maximum time is exceeded.
6868
6969
REQUEST_MEMORY_GRANT_TIMEOUT_SEC = *value*</br>
7070
Specifies the maximum time, in seconds, that a query can wait for a memory grant (work buffer memory) to become available. *value* must be 0 or a positive integer. The default setting for *value*, 0, uses an internal calculation based on query cost to determine the maximum time.
@@ -97,7 +97,7 @@ Associates the workload group with the user-defined resource pool identified by
9797
> Predefined workload groups and resource pools all use lower case names, such as "default". This should be taken into account for servers that use case-sensitive collation. Servers with case-insensitive collation, such as SQL_Latin1_General_CP1_CI_AS, will treat "default" and "Default" as the same.
9898
9999
EXTERNAL external_pool_name | "default"</br>
100-
**Applies to**: [!INCLUDE[ssNoVersion](ssnoversion-md.md)] (starting with [!INCLUDE[ssSQL15](sssql16-md.md)]).
100+
**Applies to**: [!INCLUDE[ssNoVersion](ssnoversion-md.md)] (starting with [!INCLUDE[sssql16-md](sssql16-md.md)]).
101101

102102
Workload group can specify an external resource pool. You can define a workload group and associate with two pools:
103103

‎docs/integration-services/what-s-new-in-integration-services-in-sql-server-2016.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -362,7 +362,7 @@ The latest version of the Azure Feature Pack includes the Azure SQL DW Upload ta
362362
#### <a name="ValidateXML"></a> Rich XML validation output in the XML Task
363363
Validate XML documents and get rich error output by enabling the **ValidationDetails** property of the XML Task. Before the **ValidationDetails** property was available, XML validation by the XML Task returned only a true or false result, with no information about errors or their locations. Now, when you set **ValidationDetails** to true, the output file contains detailed information about every error including the line number and the position. You can use this information to understand, locate, and fix errors in XML documents. For more info, see [Validate XML with the XML Task](../integration-services/control-flow/validate-xml-with-the-xml-task.md).
364364

365-
[!INCLUDE[ssIS](../includes/ssis-md.md)] introduced the **ValidationDetails** property in [!INCLUDE[ssSQL11](../includes/sssql11-md.md)] Service Pack 2. This new property was not announced or documented at that time. The **ValidationDetails** property is also available in [!INCLUDE[ssSQL14](../includes/sssql14-md.md)] and in [!INCLUDE[ssSQL15](../includes/sssql16-md.md)].
365+
[!INCLUDE[ssIS](../includes/ssis-md.md)] introduced the **ValidationDetails** property in [!INCLUDE[ssSQL11](../includes/sssql11-md.md)] Service Pack 2. This new property was not announced or documented at that time. The **ValidationDetails** property is also available in [!INCLUDE[ssSQL14](../includes/sssql14-md.md)] and in [!INCLUDE[sssql15-md](../includes/sssql16-md.md)].
366366

367367
[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]
368368

0 commit comments

Comments
 (0)