Skip to content

Commit 95093f8

Browse files
huypubhuypub
authored
Merge pull request #6766 from MicrosoftDocs/master
8/8 AM Publish
2 parents 0cda14b + 6d5c60a commit 95093f8

34 files changed

Lines changed: 318 additions & 427 deletions

‎.openpublishing.redirection.json‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1065,6 +1065,36 @@
10651065
"redirect_url": "/sql/t-sql/lesson-3-deleting-database-objects",
10661066
"redirect_document_id": false
10671067
},
1068+
{
1069+
"source_path": "docs/tools/dta/lesson-1-1-launching-database-engine-tuning-advisor.md",
1070+
"redirect_url": "/sql/tools/dta/lesson-1-basic-navigation-in-database-engine-tuning-advisor",
1071+
"redirect_document_id": false
1072+
},
1073+
{
1074+
"source_path": "docs/tools/dta/lesson-1-2-setting-tool-options-and-layout.md",
1075+
"redirect_url": "/sql/tools/dta/lesson-1-basic-navigation-in-database-engine-tuning-advisor",
1076+
"redirect_document_id": false
1077+
},
1078+
{
1079+
"source_path": "docs/tools/dta/lesson-1-1-tuning-a-workload.md",
1080+
"redirect_url": "/sql/tools/dta/lesson-2-using-database-engine-tuning-advisor",
1081+
"redirect_document_id": false
1082+
},
1083+
{
1084+
"source_path": "docs/tools/dta/lesson-1-2-viewing-tuning-recommendations.md",
1085+
"redirect_url": "/sql/tools/dta/lesson-2-using-database-engine-tuning-advisor",
1086+
"redirect_document_id": false
1087+
},
1088+
{
1089+
"source_path": "docs/tools/dta/lesson-1-3-viewing-tuning-reports.md",
1090+
"redirect_url": "/sql/tools/dta/lesson-2-using-database-engine-tuning-advisor",
1091+
"redirect_document_id": false
1092+
},
1093+
{
1094+
"source_path": "docs/tools/dta/ lesson-3-1-starting-the-dta-command-prompt-utility-and-tuning-a-workload.md",
1095+
"redirect_url": "/sql/tools/dta/lesson-3-using-the-dta-command-prompt-utility",
1096+
"redirect_document_id": false
1097+
},
10681098
{
10691099
"source_path": "docs/connect/php/download-microsoft-php-driver-for-sql-server.md",
10701100
"redirect_url": "/sql/connect/php/microsoft-php-driver-for-sql-server",

‎docs/database-engine/configure-windows/configure-windows-service-accounts-and-permissions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ Managed service accounts, group managed service accounts, and virtual accounts a
177177
178178
- <a name="GMSA"></a> **Group Managed Service Accounts**
179179

180-
A Group Managed Service Account is an MSA for multiple servers. Windows manages a service account for services running on a group of servers. Active Directory automatically updates the group managed service account password without restarting services. You can configure SQL Server services to use a group managed service account principal. Beginning with SQL Server 2014, SQL Server supports group managed service accounts on Windows Server 2012 R2 and later for standalone instances, failover cluster instances, and availability groups.
180+
A Group Managed Service Account is an MSA for multiple servers. Windows manages a service account for services running on a group of servers. Active Directory automatically updates the group managed service account password without restarting services. You can configure SQL Server services to use a group managed service account principal. Beginning with SQL Server 2014, SQL Server supports group managed service accounts for standalone instances, and SQL Server 2016 and later for failover cluster instances, and availability groups.
181181

182182
To use a group managed service account for SQL Server 2014 or later, the operating system must be Windows Server 2012 R2 or later. Servers with Windows Server 2012 R2 require [KB 2998082](http://support.microsoft.com/kb/2998082) applied so that the services can log in without disruption immediately after a password change.
183183

‎docs/includes/tsql-appliesto-ss2014-asdb-asdw-xxx-md.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
<Token>**THIS TOPIC APPLIES TO:**![yes](media/yes.png)SQL Server (starting with 2014)![yes](media/yes.png)Azure SQL Database![yes](media/yes.png)Azure SQL Data Warehouse ![no](media/no.png)Parallel Data Warehouse </Token>

‎docs/linux/sql-server-linux-encrypted-connections.md‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,12 @@ Before getting started, you need to make sure your certificates follow these req
2626
- The current system time must be after the Valid from property of the certificate and before the Valid to property of the certificate.
2727
- The certificate must be meant for server authentication. This requires the Enhanced Key Usage property of the certificate to specify Server Authentication (1.3.6.1.5.5.7.3.1).
2828
- The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE. Usually, the certificate's key usage property (KEY_USAGE) also includes key encipherment (CERT_KEY_ENCIPHERMENT_KEY_USAGE).
29-
- The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. Note: Wild Card Certificates are supported.
29+
- The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. Note: Wild Card Certificates are supported.
30+
31+
## Configuring the OpenSSL Libraries for Use (Optional)
32+
You can create symbolic links in the `/opt/mssql/lib/` directory that reference which `libcrypto.so` and `libssl.so` libraries should be used for encryption. This is useful if you want to force SQL Server to use a specific version of OpenSSL other than the default provided by the system. If these symbolic links are not present, SQL Server will load the default configured OpenSSL libraries on the system.
33+
34+
These symbolic links should be named `libcrypto.so` and `libssl.so` and placed in the `/opt/mssql/lib/` directory.
3035

3136
## Overview
3237
TLS is used to encrypt connections from a client application to [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. When configured correctly, TLS provides both privacy and data integrity for communications between the client and the server. TLS connections can either be client initiated or server initiated.

‎docs/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "sys.time_zone_info (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "03/27/2018"
4+
ms.date: "08/06/2018"
55
ms.prod: sql
66
ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw"
77
ms.component: "system-catalog-views"
@@ -29,7 +29,7 @@ manager: craigg
2929
monikerRange: "=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017"
3030
---
3131
# sys.time_zone_info (Transact-SQL)
32-
[!INCLUDE[tsql-appliesto-ss2014-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2014-asdb-xxxx-xxx-md.md)]
32+
[!INCLUDE[tsql-appliesto-ss2014-asdb-asdw-xxx-md](../../includes/tsql-appliesto-ss2014-asdb-asdw-xxx-md.md)]
3333

3434
Returns information about supported time zones. All time zones installed on the computer are stored in the following registry hive:
3535
`KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones`.

‎docs/t-sql/statements/alter-database-transact-sql-set-options.md‎

Lines changed: 38 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ SET
112112
}
113113
}
114114
115-
<change_tracking_option_list> ::=
115+
<change_tracking_option_list> ::=
116116
{
117117
AUTO_CLEANUP = { ON | OFF }
118118
| CHANGE_RETENTION = retention_period { DAYS | HOURS | MINUTES }
@@ -1306,7 +1306,7 @@ SET
13061306
}
13071307
13081308
<automatic_tuning_option> ::=
1309-
{ AUTOMATIC_TUNING = { AUTO | INHERIT | CUSTOM }
1309+
{ AUTOMATIC_TUNING = { AUTO | INHERIT | CUSTOM }
13101310
| AUTOMATIC_TUNING ( CREATE_INDEX = { DEFAULT | ON | OFF } )
13111311
| AUTOMATIC_TUNING ( DROP_INDEX = { DEFAULT | ON | OFF } )
13121312
| AUTOMATIC_TUNING ( FORCE_LAST_GOOD_PLAN = { DEFAULT | ON | OFF } )
@@ -1322,7 +1322,7 @@ SET
13221322
}
13231323
}
13241324
1325-
<change_tracking_option_list> ::=
1325+
<change_tracking_option_list> ::=
13261326
{
13271327
AUTO_CLEANUP = { ON | OFF }
13281328
| CHANGE_RETENTION = retention_period { DAYS | HOURS | MINUTES }
@@ -1483,54 +1483,54 @@ For more information that describes when to use synchronous or asynchronous stat
14831483
<a name="auto_tuning"></a> **\<automatic_tuning_option> ::=**
14841484
**Applies to**: [!INCLUDE[sssqlv14-md](../../includes/sssqlv14-md.md)].
14851485

1486-
Controls automatic options for [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
1486+
Controls automatic options for [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
14871487

1488-
AUTOMATIC_TUNING = { AUTO | INHERIT | CUSTOM }
1489-
AUTO
1490-
Setting the automatic tuning value to AUTO will apply Azure configuration defaults for automatic tuning.
1488+
AUTOMATIC_TUNING = { AUTO | INHERIT | CUSTOM }
1489+
AUTO
1490+
Setting the automatic tuning value to AUTO will apply Azure configuration defaults for automatic tuning.
1491+
1492+
INHERIT
1493+
Using the value INHERIT will inherit the default configuration from the parent server. This is especially useful if you would like to customize automatic tuning configuration on a parent server, and have all the databases on such server INHERIT these custom settings. Please note that in order for the inheritance to work, the three individual tuning options FORCE_LAST_GOOD_PLAN, CREATE_INDEX and DROP_INDEX need to be set to DEFAULT on databases.
14911494

1492-
INHERIT
1493-
Using the value INHERIT will inherit the default configuration from the parent server. This is especially useful if you would like to customize automatic tuning configuration on a parent server, and have all the databases on such server INHERIT these custom settings. Please note that in order for the inheritance to work, the three individual tuning options FORCE_LAST_GOOD_PLAN, CREATE_INDEX and DROP_INDEX need to be set to DEFAULT on databases.
1494-
1495-
CUSTOM
1496-
Using the value CUSTOM, you will need to manually custom configure each of the automatic tuning options available on databases.
1495+
CUSTOM
1496+
Using the value CUSTOM, you will need to manually custom configure each of the automatic tuning options available on databases.
1497+
1498+
Enables or disables automatic index management `CREATE_INDEX` option of [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
14971499

1498-
Enables or disables automatic index management `CREATE_INDEX` option of [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
1499-
15001500
CREATE_INDEX = { DEFAULT | ON | OFF }
1501-
DEFALT
1502-
Inherits default settings from the server. In this case, options of enabling or disabling individual Automatic tuning features are defined at the server level.
1503-
1504-
ON
1501+
DEFALT
1502+
Inherits default settings from the server. In this case, options of enabling or disabling individual Automatic tuning features are defined at the server level.
1503+
1504+
ON
15051505
When enabled, missing indexes are automatically generated on a database. Following the index creation, gains to the performance of the workload are verified. When such created index no longer provides benefits to the workload performance, it is automatically reverted. Indexes automatically created are flagged as a system generated indexed.
1506-
1507-
OFF
1508-
Does not automatically generate missing indexes on the database.
1509-
1510-
Enables or disables automatic index management `DROP_INDEX` option of [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
1511-
1506+
1507+
OFF
1508+
Does not automatically generate missing indexes on the database.
1509+
1510+
Enables or disables automatic index management `DROP_INDEX` option of [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
1511+
15121512
DROP_INDEX = { DEFAULT | ON | OFF }
1513-
DEFALT
1514-
Inherits default settings from the server. In this case, options of enabling or disabling individual Automatic tuning features are defined at the server level.
1513+
DEFALT
1514+
Inherits default settings from the server. In this case, options of enabling or disabling individual Automatic tuning features are defined at the server level.
15151515

1516-
ON
1517-
Automatically drops duplicate or no longer useful indexes to the performance workload.
1516+
ON
1517+
Automatically drops duplicate or no longer useful indexes to the performance workload.
1518+
1519+
OFF
1520+
Does not automatically drop missing inexes on the database.
1521+
1522+
Enables or disables automatic plan correction `FORCE_LAST_GOOD_PLAN` option of [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
15181523

1519-
OFF
1520-
Does not automatically drop missing inexes on the database.
1521-
1522-
Enables or disables automatic plan correction `FORCE_LAST_GOOD_PLAN` option of [automatic tuning](../../relational-databases/automatic-tuning/automatic-tuning.md).
1523-
15241524
FORCE_LAST_GOOD_PLAN = { DEFAULT | ON | OFF }
1525-
DEFAULT
1526-
Inherits default settings from the server. In this case, options of enabling or disabling individual Automatic tuning features are defined at the server level.
1525+
DEFAULT
1526+
Inherits default settings from the server. In this case, options of enabling or disabling individual Automatic tuning features are defined at the server level.
15271527

15281528
ON
15291529
The [!INCLUDE[ssde_md](../../includes/ssde_md.md)] automatically forces the last known good plan on the [!INCLUDE[tsql_md](../../includes/tsql_md.md)] queries where new SQL plan causes performance regressions. The [!INCLUDE[ssde_md](../../includes/ssde_md.md)] continously monitors query performance of the [!INCLUDE[tsql_md](../../includes/tsql_md.md)] query with the forced plan. If there are performance gains, the [!INCLUDE[ssde_md](../../includes/ssde_md.md)] will keep using last known good plan. If performance gains are not detected, the [!INCLUDE[ssde_md](../../includes/ssde_md.md)] will produce a new SQL plan. The statement will fail if Query Store is not enabled or if it is not in *Read-Write* mode.
15301530

15311531
OFF
1532-
The [!INCLUDE[ssde_md](../../includes/ssde_md.md)] reports potential query performance regressions caused by SQL plan changes in [sys.dm_db_tuning_recommendations](../../relational-databases/system-dynamic-management-views/sys-dm-db-tuning-recommendations-transact-sql.md) view. However, these recommendations are not automatically applied. User can monitor active recomendations and fix identified problems by applying [!INCLUDE[tsql_md](../../includes/tsql_md.md)] scripts that are shown in the view. This is the default value.
1533-
1532+
The [!INCLUDE[ssde_md](../../includes/ssde_md.md)] reports potential query performance regressions caused by SQL plan changes in [sys.dm_db_tuning_recommendations](../../relational-databases/system-dynamic-management-views/sys-dm-db-tuning-recommendations-transact-sql.md) view. However, these recommendations are not automatically applied. User can monitor active recomendations and fix identified problems by applying [!INCLUDE[tsql_md](../../includes/tsql_md.md)] scripts that are shown in the view. This is the default value.
1533+
15341534
**\<change_tracking_option> ::=**
15351535

15361536
Controls change tracking options. You can enable change tracking, set options, change options, and disable change tracking. For examples, see the Examples section later in this article.
@@ -2092,7 +2092,7 @@ SET
20922092
}
20932093
}
20942094
2095-
<change_tracking_option_list> ::=
2095+
<change_tracking_option_list> ::=
20962096
{
20972097
AUTO_CLEANUP = { ON | OFF }
20982098
| CHANGE_RETENTION = retention_period { DAYS | HOURS | MINUTES }

‎docs/t-sql/statements/alter-database-transact-sql.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,15 +32,15 @@ monikerRange: ">=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-current||
3232
---
3333
# ALTER DATABASE (Transact-SQL)
3434

35-
Modifies a database.
35+
Modifies certain configuration options of a database.
3636

37-
Click one of the following tabs for the syntax, arguments, remarks, permissions, and examples for a particular SQL version with which you are working.
37+
This article provides the syntax, arguments, remarks, permissions, and examples for whichever SQL product you choose.
3838

3939
For more information about the syntax conventions, see [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md).
4040

4141
## Click a product!
4242

43-
In the following row, click whichever product name you are interested in. The click displays different content here, appropriate for whichever product you click:
43+
In the following row, click whichever product name you are interested in. The click displays different content here on this webpage, appropriate for whichever product you click.
4444

4545
::: moniker range=">=sql-server-2016||>=sql-server-linux-2017||=sqlallproducts-allversions"
4646

0 commit comments

Comments
 (0)