Skip to content

Commit e608013

Browse files
SaisangSaisang
committed
escape @ character
1 parent 410fbce commit e608013

32 files changed

Lines changed: 167 additions & 167 deletions

File tree

‎docs/database-engine/availability-groups/windows/maintaining-an-always-on-publication-database-sql-server.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,17 +26,17 @@ ms.author: mathoma
2626

2727
- Replication Monitor always displays publication information under the original publisher. However, this information can be viewed in Replication Monitor from any replica by adding the original publisher as a server.
2828

29-
- When using stored procedures or Replication Management Objects (RMO) to administer replication at the current primary, for cases in which you specify the Publisher name, you must specify the name of the instance on which the database was enabled for replication (the original publisher). To determine the appropriate name, use the **PUBLISHINGSERVERNAME** function. When a publishing database joins an availability group, the replication metadata stored in the secondary database replicas is identical to that at the primary. Consequently, for publication databases enabled for replication at the primary, the publisher instance name stored in system tables at the secondary is the name of the primary, not the secondary. This affects replication configuration and maintenance if the publication database fails over to a secondary. For example, if you are configuring replication with stored procedures at a secondary after failover, and you want a pull subscription to a publication database that was enabled at a different replica, you must specify the name of the original publisher instead of the current publisher as the *@publisher* parameter of **sp_addpullsubscription** or **sp_addmergepulllsubscription**. However, if you enable a publication database after failover, the publisher instance name stored in the system tables is the name of the current primary host. In this case, you would use the host name of the current primary replica for the *@publisher* parameter.
29+
- When using stored procedures or Replication Management Objects (RMO) to administer replication at the current primary, for cases in which you specify the Publisher name, you must specify the name of the instance on which the database was enabled for replication (the original publisher). To determine the appropriate name, use the **PUBLISHINGSERVERNAME** function. When a publishing database joins an availability group, the replication metadata stored in the secondary database replicas is identical to that at the primary. Consequently, for publication databases enabled for replication at the primary, the publisher instance name stored in system tables at the secondary is the name of the primary, not the secondary. This affects replication configuration and maintenance if the publication database fails over to a secondary. For example, if you are configuring replication with stored procedures at a secondary after failover, and you want a pull subscription to a publication database that was enabled at a different replica, you must specify the name of the original publisher instead of the current publisher as the *\@publisher* parameter of **sp_addpullsubscription** or **sp_addmergepulllsubscription**. However, if you enable a publication database after failover, the publisher instance name stored in the system tables is the name of the current primary host. In this case, you would use the host name of the current primary replica for the *\@publisher* parameter.
3030

3131
> [!NOTE]
32-
> For some procedures, such as **sp_addpublication**, the *@publisher* parameter is supported only for publishers that are not instances of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]; in these cases, it is not relevant for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Always On.
32+
> For some procedures, such as **sp_addpublication**, the *\@publisher* parameter is supported only for publishers that are not instances of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]; in these cases, it is not relevant for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Always On.
3333
3434
- To synchronize a subscription in [!INCLUDE[ssManStudio](../../../includes/ssmanstudio-md.md)] after a failover, synchronize pull subscriptions from the subscriber and synchronize push subscriptions from the active publisher.
3535

3636
## <a name="RemovePublDb"></a> Removing a Published Database from an Availability Group
3737
Consider the following issues if a published database is removed from an availability group, or if an availability group that has a published member database is dropped.
3838

39-
- If the publication database at the original publisher is removed from an availability group primary replica, you must run **sp_redirect_publisher** without specifying a value for the *@redirected_publisher* parameter in order to remove the redirection for the publisher/database pair.
39+
- If the publication database at the original publisher is removed from an availability group primary replica, you must run **sp_redirect_publisher** without specifying a value for the *\@redirected_publisher* parameter in order to remove the redirection for the publisher/database pair.
4040

4141
```
4242
EXEC sys.sp_redirect_publisher
@@ -62,7 +62,7 @@ ms.author: mathoma
6262
> [!NOTE]
6363
> When an availability group is removed that has published member databases, or a published database is removed from an availability group, all copies of the published databases will be left in the recovering state. If restored, each will appear as a published database. Only one copy should be retained with publication metadata. To disable replication for a published database copy, first remove all subscriptions and publications from the database.
6464
65-
Run **sp_dropsubscription** to remove publication subscriptions. Make sure to set the parameter *@ignore_distributor* to 1 to preserve the metadata for the active publishing database at the distributor.
65+
Run **sp_dropsubscription** to remove publication subscriptions. Make sure to set the parameter *\@ignore_distributor* to 1 to preserve the metadata for the active publishing database at the distributor.
6666
6767
```
6868
USE MyDBName;
@@ -75,7 +75,7 @@ ms.author: mathoma
7575
@ignore_distributor = 1;
7676
```
7777
78-
Run **sp_droppublication** to remove all publications. Again, set the parameter *@ignore_distributor* to 1 to preserve the metadata for the active publishing database at the distributor.
78+
Run **sp_droppublication** to remove all publications. Again, set the parameter *\@ignore_distributor* to 1 to preserve the metadata for the active publishing database at the distributor.
7979
8080
```
8181
EXEC sys.sp_droppublication

‎docs/database-engine/database-mirroring/database-mirroring-use-certificates-for-outbound-connections.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ ms.author: mikeray
5858
For example, to create a certificate for the HOST_A system.
5959
6060
> [!IMPORTANT]
61-
> If you intend to use the certificate for more than one year, specify the expiry date in UTC time by using the EXPIRY_DATE option in your CREATE CERTIFICATE statement. Also, we recommend that you use SQL Server Management Studio to create a Policy-Based Management rule to alert you when your certificates are expiring. Using the Policy Management **Create New Condition** dialog box, create this rule on the **@ExpirationDate** field of the **Certificate** facet. For more information, see [Administer Servers by Using Policy-Based Management](../../relational-databases/policy-based-management/administer-servers-by-using-policy-based-management.md) and [Securing SQL Server](../../relational-databases/security/securing-sql-server.md).
61+
> If you intend to use the certificate for more than one year, specify the expiry date in UTC time by using the EXPIRY_DATE option in your CREATE CERTIFICATE statement. Also, we recommend that you use SQL Server Management Studio to create a Policy-Based Management rule to alert you when your certificates are expiring. Using the Policy Management **Create New Condition** dialog box, create this rule on the **\@ExpirationDate** field of the **Certificate** facet. For more information, see [Administer Servers by Using Policy-Based Management](../../relational-databases/policy-based-management/administer-servers-by-using-policy-based-management.md) and [Securing SQL Server](../../relational-databases/security/securing-sql-server.md).
6262
6363
```
6464
USE master;

‎docs/relational-databases/backup-restore/disable-sql-server-managed-backup-to-microsoft-azure.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: mikeray
1616
This topic describes how to disable or pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] at both the database and instance levels.
1717

1818
## <a name="DatabaseDisable"></a> Disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] for a database
19-
You can disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] settings by using the system stored procedure, [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). The *@enable_backup* parameter is used to enable and disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] configurations for a specific database, where 1 enables and 0 disables the configuration settings.
19+
You can disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] settings by using the system stored procedure, [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). The *\@enable_backup* parameter is used to enable and disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] configurations for a specific database, where 1 enables and 0 disables the configuration settings.
2020

2121
#### To Disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] for a specific database:
2222

@@ -103,7 +103,7 @@ GO
103103
```
104104

105105
## <a name="InstanceDisable"></a> Disable Default [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] settings for the Instance
106-
Default settings at the instance level apply to all new databases created on that instance. If you no longer need or require default settings, you can disable this configuration by using the **managed_backup.sp_backup_config_basic** system stored procedure with the *@database_name* parameter set to NULL. Disabling does not remove the other configuration settings like the storage URL, retention setting, or the SQL Credential name. These settings will be used if [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] is enabled for the instance at a later time.
106+
Default settings at the instance level apply to all new databases created on that instance. If you no longer need or require default settings, you can disable this configuration by using the **managed_backup.sp_backup_config_basic** system stored procedure with the *\@database_name* parameter set to NULL. Disabling does not remove the other configuration settings like the storage URL, retention setting, or the SQL Credential name. These settings will be used if [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] is enabled for the instance at a later time.
107107

108108
#### To disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] default configuration settings:
109109

@@ -121,7 +121,7 @@ GO
121121
```
122122
123123
## <a name="InstancePause"></a> Pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] at the Instance Level
124-
There might be times when you need to temporarily pause the [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] services for a short period time. The **managed_backup.sp_backup_master_switch** system stored procedure allows you to disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] service at the instance level. The same stored procedure is used to resume [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]. The @state parameter is used to define whether [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] should be turned off or on.
124+
There might be times when you need to temporarily pause the [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] services for a short period time. The **managed_backup.sp_backup_master_switch** system stored procedure allows you to disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] service at the instance level. The same stored procedure is used to resume [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]. The \@state parameter is used to define whether [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] should be turned off or on.
125125
126126
#### To Pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] Services Using Transact-SQL:
127127

‎docs/relational-databases/in-memory-oltp/create-and-access-tables-in-tempdb-from-stored-procedures.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
1919

2020
For more details about memory-optimization of temp table and table variable scenarios see: [Faster temp table and table variable by using memory optimization](../../relational-databases/in-memory-oltp/faster-temp-table-and-table-variable-by-using-memory-optimization.md).
2121

22-
The following example shows how the use of a temp table with three columns (id, ProductID, Quantity) can be replaced using a table variable **@OrderQuantityByProduct** of type **dbo.OrderQuantityByProduct**:
22+
The following example shows how the use of a temp table with three columns (id, ProductID, Quantity) can be replaced using a table variable **\@OrderQuantityByProduct** of type **dbo.OrderQuantityByProduct**:
2323

2424
```sql
2525
CREATE TYPE dbo.OrderQuantityByProduct

‎docs/relational-databases/replication/administration/configure-the-transaction-set-job-for-an-oracle-publisher.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,27 +24,27 @@ ms.author: "mathoma"
2424

2525
1. At the Oracle Publisher, set the **job_queue_processes** initialization parameter to a sufficient value to allow the Xactset job run. For more information about this parameter, see the database documentation for the Oracle Publisher.
2626

27-
2. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**, a value of **xactsetbatching** for **@propertyname**, and a value of **enabled** for **@propertyvalue**.
27+
2. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**, a value of **xactsetbatching** for **\@propertyname**, and a value of **enabled** for **\@propertyvalue**.
2828

29-
3. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**, a value of **xactsetjobinterval** for **@propertyname**, and the job interval, in minutes, for **@propertyvalue**.
29+
3. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**, a value of **xactsetjobinterval** for **\@propertyname**, and the job interval, in minutes, for **\@propertyvalue**.
3030

31-
4. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**, a value of **xactsetjob** for **@propertyname**, and a value of **enabled** for **@propertyvalue**.
31+
4. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**, a value of **xactsetjob** for **\@propertyname**, and a value of **enabled** for **\@propertyvalue**.
3232

3333
### To configure the transaction set job
3434

35-
1. (Optional) At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**. This returns properties of the **Xactset** job at the Publisher.
35+
1. (Optional) At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**. This returns properties of the **Xactset** job at the Publisher.
3636

37-
2. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**, the name of the Xactset job property being set for **@propertyname**, and new setting for **@propertyvalue**.
37+
2. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**, the name of the Xactset job property being set for **\@propertyname**, and new setting for **\@propertyvalue**.
3838

3939
3. (Optional) Repeat step 2 for each Xactset job property being set. When changing the **xactsetjobinterval** property, you must restart the job on the Oracle Publisher for the new interval to take effect.
4040

4141
### To view properties of the transaction set job
4242

43-
1. At the Distributor, execute [sp_helpxactsetjob](../../../relational-databases/system-stored-procedures/sp-helpxactsetjob-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**.
43+
1. At the Distributor, execute [sp_helpxactsetjob](../../../relational-databases/system-stored-procedures/sp-helpxactsetjob-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**.
4444

4545
### To disable the transaction set job
4646

47-
1. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **@publisher**, a value of **xactsetjob** for **@propertyname**, and a value of **disabled** for **@propertyvalue**.
47+
1. At the Distributor, execute [sp_publisherproperty &#40;Transact-SQL&#41;](../../../relational-databases/system-stored-procedures/sp-publisherproperty-transact-sql.md). Specify the name of the Oracle Publisher for **\@publisher**, a value of **xactsetjob** for **\@propertyname**, and a value of **disabled** for **\@propertyvalue**.
4848

4949
## Example
5050
The following example enables the `Xactset` job and sets an interval of three minutes between runs.

0 commit comments

Comments
 (0)