Merge pull request #12127 from MicrosoftDocs/master

huypub · web-flow · commit 0ea19d8e3bd9 · 2019-09-20T15:29:09.000-07:00
9/20 PM Publish
diff --git a/docs/big-data-cluster/deployment-guidance.md b/docs/big-data-cluster/deployment-guidance.md
@@ -143,7 +143,7 @@ The following environment variables are used for security settings that are not
 | **CONTROLLER_PASSWORD** | Required |The password for the cluster administrator. |
 | **MSSQL_SA_PASSWORD** | Required |The password of SA user for SQL master instance. |
 | **KNOX_PASSWORD** | Required |The password for Knox **root** user. Note than in a basic authentication setup only user supported for Knox is **root**.|
-| **ACCEPT_EULA**| Required for first use of `azdata`| Requires no value. When set as an environment variable, it applies EULA to both SQL Server and `azdata`. If not set as environment variable, you can include `--accept-eula` in the first use of `azdata` command.|
+| **ACCEPT_EULA**| Required for first use of `azdata`| Set to "yes". When set as an environment variable, it applies EULA to both SQL Server and `azdata`. If not set as environment variable, you can include `--accept-eula=yes` in the first use of `azdata` command.|
 | **DOCKER_USERNAME** | Optional | The username to access the container images in case they are stored in a private repository. See the [Offline deployments](deploy-offline.md) topic for more details on how to use a private Docker repository for big data cluster deployment.|
 | **DOCKER_PASSWORD** | Optional |The password to access the above private repository. |
 
@@ -156,6 +156,7 @@ export CONTROLLER_USERNAME=admin
 export CONTROLLER_PASSWORD=<password>
 export MSSQL_SA_PASSWORD=<password>
 export KNOX_PASSWORD=<password>
+export ACCEPT_EULA=yes
 ```
 
 ```PowerShell
diff --git a/docs/relational-databases/errors-events/mssqlserver-10536-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-10536-database-engine-error.md
@@ -24,10 +24,10 @@ ms.author: mathoma
 |Event Source|MSSQLSERVER|  
 |Component|SQLEngine|  
 |Symbolic Name|PG_TOO_MANY_STMTS|  
-|Message Text|Cannot create plan guide '%.\*ls' because the batch or module corresponding to the specified **@plan_handle** contains more than 1000 eligible statements. Create a plan guide for each statement in the batch or module by specifying a **statement_start_offset** value for each statement.|  
+|Message Text|Cannot create plan guide '%.\*ls' because the batch or module corresponding to the specified **\@plan_handle** contains more than 1000 eligible statements. Create a plan guide for each statement in the batch or module by specifying a **statement_start_offset** value for each statement.|  
   
 ## Explanation  
-The batch or module corresponding to the specified **@plan_handle** contains more than 1000 eligible statements.  
+The batch or module corresponding to the specified **\@plan_handle** contains more than 1000 eligible statements.  
   
 ## User Action  
 Create a plan guide for each statement in the batch or module by specifying a **statement_start_offset** value for each statement.  
diff --git a/docs/relational-databases/replication/administration/frequently-asked-questions-for-replication-administrators.md b/docs/relational-databases/replication/administration/frequently-asked-questions-for-replication-administrators.md
@@ -148,7 +148,7 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2014||=sqlallproducts-allver
   
 -   Specify that objects should not be dropped when the subscription is reinitialized. Prior to reinitialization, either:  
   
-    -   Execute [sp_changearticle](../../../relational-databases/system-stored-procedures/sp-changearticle-transact-sql.md) or [sp_changemergearticle](../../../relational-databases/system-stored-procedures/sp-changemergearticle-transact-sql.md). Specify a value of 'pre_creation_cmd' (**sp_changearticle**) or 'pre_creation_command' (**sp_changemergearticle**) for the parameter **@property** and a value of 'none', 'delete' or 'truncate' for the parameter **@value**.  
+    -   Execute [sp_changearticle](../../../relational-databases/system-stored-procedures/sp-changearticle-transact-sql.md) or [sp_changemergearticle](../../../relational-databases/system-stored-procedures/sp-changemergearticle-transact-sql.md). Specify a value of 'pre_creation_cmd' (**sp_changearticle**) or 'pre_creation_command' (**sp_changemergearticle**) for the parameter **\@property** and a value of 'none', 'delete' or 'truncate' for the parameter **\@value**.  
   
     -   In the **Article Properties - \<Article>** dialog box in the **Destination Object** section, select a value of **Keep existing object unchanged**, **Delete data. If article has a row filter, delete only data that matches the filter.** or **Truncate all data in the existing object** for the option **Action if name is in use**. For more information on accessing this dialog box, see [View and Modify Publication Properties](../../../relational-databases/replication/publish/view-and-modify-publication-properties.md).  
   
diff --git a/docs/relational-databases/replication/administration/upgrade-replication-scripts-replication-transact-sql-programming.md b/docs/relational-databases/replication/administration/upgrade-replication-scripts-replication-transact-sql-programming.md
diff --git a/docs/relational-databases/replication/publish/view-and-modify-article-properties.md b/docs/relational-databases/replication/publish/view-and-modify-article-properties.md
@@ -98,29 +98,29 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2014||=sqlallproducts-allver
   
 #### To view the properties of an article belonging to a snapshot or transactional publication  
   
-1.  Execute [sp_helparticle](../../../relational-databases/system-stored-procedures/sp-helparticle-transact-sql.md), specifying the name of the publication for the **@publication** parameter and the name of the article for the **@article** parameter. If you do not specify **@article**, information will be returned for all articles in the publication.  
+1.  Execute [sp_helparticle](../../../relational-databases/system-stored-procedures/sp-helparticle-transact-sql.md), specifying the name of the publication for the **\@publication** parameter and the name of the article for the **\@article** parameter. If you do not specify **\@article**, information will be returned for all articles in the publication.  
   
 2.  Execute [sp_helparticlecolumns](../../../relational-databases/system-stored-procedures/sp-helparticlecolumns-transact-sql.md) for table articles to list all columns available in the base table.  
   
 #### To modify the properties of an article belonging to a snapshot or transactional publication  
   
-1.  Execute [sp_changearticle](../../../relational-databases/system-stored-procedures/sp-changearticle-transact-sql.md), specifying the article property being changed in the **@property** parameter and the new value of this property in the **@value** parameter.  
+1.  Execute [sp_changearticle](../../../relational-databases/system-stored-procedures/sp-changearticle-transact-sql.md), specifying the article property being changed in the **\@property** parameter and the new value of this property in the **\@value** parameter.  
   
     > [!NOTE]  
-    >  If the change requires the generation of a new snapshot, you must also specify a value of **1** for **@force_invalidate_snapshot**, and if the change requires that Subscribers be reinitialized, you must also specify a value of **1** for **@force_reinit_subscription**. For more information on the properties that, when changed, require a new snapshot or reinitialization, see [Change Publication and Article Properties](../../../relational-databases/replication/publish/change-publication-and-article-properties.md).  
+    >  If the change requires the generation of a new snapshot, you must also specify a value of **1** for **\@force_invalidate_snapshot**, and if the change requires that Subscribers be reinitialized, you must also specify a value of **1** for **\@force_reinit_subscription**. For more information on the properties that, when changed, require a new snapshot or reinitialization, see [Change Publication and Article Properties](../../../relational-databases/replication/publish/change-publication-and-article-properties.md).  
   
 #### To view the properties of an article belonging to a merge publication  
   
-1.  Execute [sp_helpmergearticle](../../../relational-databases/system-stored-procedures/sp-helpmergearticle-transact-sql.md), specifying the name of the publication for the **@publication** parameter and the name of the article for the **@article** parameter. If you do not specify these parameters, information will be returned for all articles in a publication or at the publisher.  
+1.  Execute [sp_helpmergearticle](../../../relational-databases/system-stored-procedures/sp-helpmergearticle-transact-sql.md), specifying the name of the publication for the **\@publication** parameter and the name of the article for the **\@article** parameter. If you do not specify these parameters, information will be returned for all articles in a publication or at the publisher.  
   
 2.  Execute [sp_helpmergearticlecolumn](../../../relational-databases/system-stored-procedures/sp-helpmergearticlecolumn-transact-sql.md) for table articles to list all columns available in the base table.  
   
 #### To modify the properties of an article belonging to a merge publication  
   
-1.  Execute [sp_changemergearticle](../../../relational-databases/system-stored-procedures/sp-changemergearticle-transact-sql.md), specifying the article property being changed in the **@property** parameter and the new value of this property in the **@value** parameter.  
+1.  Execute [sp_changemergearticle](../../../relational-databases/system-stored-procedures/sp-changemergearticle-transact-sql.md), specifying the article property being changed in the **\@property** parameter and the new value of this property in the **\@value** parameter.  
   
     > [!NOTE]  
-    >  If the change requires the generation of a new snapshot, you must also specify a value of **1** for **@force_invalidate_snapshot**, and if the change requires that Subscribers be reinitialized, you must also specify a value of **1** for **@force_reinit_subscription**. For more information on the properties that, when changed, require a new snapshot or reinitialization, see [Change Publication and Article Properties](../../../relational-databases/replication/publish/change-publication-and-article-properties.md).  
+    >  If the change requires the generation of a new snapshot, you must also specify a value of **1** for **\@force_invalidate_snapshot**, and if the change requires that Subscribers be reinitialized, you must also specify a value of **1** for **\@force_reinit_subscription**. For more information on the properties that, when changed, require a new snapshot or reinitialization, see [Change Publication and Article Properties](../../../relational-databases/replication/publish/change-publication-and-article-properties.md).  
   
 ###  <a name="TsqlExample"></a> Example (Transact-SQL)  
  This transactional replication example returns the properties of the published article.  
diff --git a/docs/relational-databases/replication/view-and-modify-push-subscription-properties.md b/docs/relational-databases/replication/view-and-modify-push-subscription-properties.md
@@ -58,23 +58,23 @@ monikerRange: "=azuresqldb-current||>=sql-server-2014||=sqlallproducts-allversio
   
 #### To view the properties of a push subscription to a snapshot or transactional publication  
   
-1.  At the Publisher on the publication database, execute [sp_helpsubscription](../../relational-databases/system-stored-procedures/sp-helpsubscription-transact-sql.md). Specify **@publication**, **@subscriber**, and a value of **all** for **@article**.  
+1.  At the Publisher on the publication database, execute [sp_helpsubscription](../../relational-databases/system-stored-procedures/sp-helpsubscription-transact-sql.md). Specify **\@publication**, **\@subscriber**, and a value of **all** for **\@article**.  
   
-2.  At the Publisher on the publication database, execute [sp_helpsubscriberinfo](../../relational-databases/system-stored-procedures/sp-helpsubscriberinfo-transact-sql.md), specifying **@subscriber**.  
+2.  At the Publisher on the publication database, execute [sp_helpsubscriberinfo](../../relational-databases/system-stored-procedures/sp-helpsubscriberinfo-transact-sql.md), specifying **\@subscriber**.  
   
 #### To change the properties of a push subscription to a snapshot or transactional publication  
   
-1.  At the Publisher on the publication database, execute [sp_changesubscriber](../../relational-databases/system-stored-procedures/sp-changesubscriber-transact-sql.md), specifying **@subscriber** and any parameters for the Subscriber properties being changed.  
+1.  At the Publisher on the publication database, execute [sp_changesubscriber](../../relational-databases/system-stored-procedures/sp-changesubscriber-transact-sql.md), specifying **\@subscriber** and any parameters for the Subscriber properties being changed.  
   
-2.  At the Publisher on the publication database, execute [sp_changesubscription](../../relational-databases/system-stored-procedures/sp-changesubscription-transact-sql.md). Specify **@publication**, **@subscriber**, **@destination_db**, a value of **all** for **@article**, the subscription property being changed as **@property**, and the new value as **@value**. This changes security settings for the push subscription.  
+2.  At the Publisher on the publication database, execute [sp_changesubscription](../../relational-databases/system-stored-procedures/sp-changesubscription-transact-sql.md). Specify **\@publication**, **\@subscriber**, **\@destination_db**, a value of **all** for **\@article**, the subscription property being changed as **\@property**, and the new value as **\@value**. This changes security settings for the push subscription.  
   
-3.  (Optional) To change the Data Transformation Services (DTS) package properties of a subscription, execute [sp_changesubscriptiondtsinfo](../../relational-databases/system-stored-procedures/sp-changesubscriptiondtsinfo-transact-sql.md) at the Subscriber on the subscription database. Specify the ID of the Distribution Agent job for **@jobid** and the following DTS package properties:  
+3.  (Optional) To change the Data Transformation Services (DTS) package properties of a subscription, execute [sp_changesubscriptiondtsinfo](../../relational-databases/system-stored-procedures/sp-changesubscriptiondtsinfo-transact-sql.md) at the Subscriber on the subscription database. Specify the ID of the Distribution Agent job for **\@jobid** and the following DTS package properties:  
   
-    -   **@dts_package_name**  
+    -   **\@dts_package_name**  
   
-    -   **@dts_package_password**  
+    -   **\@dts_package_password**  
   
-    -   **@dts_package_location**  
+    -   **\@dts_package_location**  
   
      This changes the DTS package properties of a subscription.  
   
@@ -83,13 +83,13 @@ monikerRange: "=azuresqldb-current||>=sql-server-2014||=sqlallproducts-allversio
   
 #### To view the properties of a push subscription to a merge publication  
   
-1.  At the Publisher on the publication database, execute [sp_helpmergesubscription](../../relational-databases/system-stored-procedures/sp-helpmergesubscription-transact-sql.md). Specify **@publication** and **@subscriber**.  
+1.  At the Publisher on the publication database, execute [sp_helpmergesubscription](../../relational-databases/system-stored-procedures/sp-helpmergesubscription-transact-sql.md). Specify **\@publication** and **\@subscriber**.  
   
-2.  At the Publisher, execute [sp_helpsubscriberinfo](../../relational-databases/system-stored-procedures/sp-helpsubscriberinfo-transact-sql.md), specifying **@subscriber**.  
+2.  At the Publisher, execute [sp_helpsubscriberinfo](../../relational-databases/system-stored-procedures/sp-helpsubscriberinfo-transact-sql.md), specifying **\@subscriber**.  
   
 #### To change the properties of a push subscription to a merge publication  
   
-1.  At the Publisher on the publication database, execute [sp_changemergesubscription](../../relational-databases/system-stored-procedures/sp-changemergesubscription-transact-sql.md). Specify **@publication**, **@subscriber**, **@subscriber_db**, the subscription property being changed as **@property**, and the new value as **@value**.  
+1.  At the Publisher on the publication database, execute [sp_changemergesubscription](../../relational-databases/system-stored-procedures/sp-changemergesubscription-transact-sql.md). Specify **\@publication**, **\@subscriber**, **\@subscriber_db**, the subscription property being changed as **\@property**, and the new value as **\@value**.  
   
 ###  <a name="TsqlExample"></a> Example (Transact-SQL)  
   
diff --git a/docs/relational-databases/system-stored-procedures/sp-add-alert-transact-sql.md b/docs/relational-databases/system-stored-procedures/sp-add-alert-transact-sql.md
@@ -152,7 +152,7 @@ sp_add_alert [ @name = ] 'name'
   
 -   The alert is enabled.  
   
--   Events generated with **xp_logevent** occur in the master database. Therefore, **xp_logevent** does not trigger an alert unless the **@database_name** for the alert is **'master'** or NULL.  
+-   Events generated with **xp_logevent** occur in the master database. Therefore, **xp_logevent** does not trigger an alert unless the **\@database_name** for the alert is **'master'** or NULL.  
   
 ## Permissions  
  By default, only members of the **sysadmin** fixed server role can execute **sp_add_alert**.  
diff --git a/docs/relational-databases/system-stored-procedures/sp-send-dbmail-transact-sql.md b/docs/relational-databases/system-stored-procedures/sp-send-dbmail-transact-sql.md
diff --git a/docs/t-sql/language-elements/fetch-transact-sql.md b/docs/t-sql/language-elements/fetch-transact-sql.md
