Skip to content

Commit 0596361

Browse files
SaisangSaisang
committed
bulk fix triple asterisks
1 parent f41bea4 commit 0596361

80 files changed

Lines changed: 297 additions & 297 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/2014/relational-databases/indexes/delete-an-index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ manager: craigg
7676

7777
7. Click **Close**.
7878

79-
8. On the **File** menu, select **Save***table_name*.
79+
8. On the **File** menu, select **Save**_table_name_.
8080

8181
## <a name="TsqlProcedure"></a> Using Transact-SQL
8282

‎docs/2014/relational-databases/tables/delete-primary-keys.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ manager: craigg
5757
> [!NOTE]
5858
> To undo this action, close the table without saving the changes. Deleting a primary key cannot be undone without losing all other changes made to the table.
5959
60-
3. On the **File** menu, click **Save***table name*.
60+
3. On the **File** menu, click **Save**_table name_.
6161

6262
## <a name="TsqlProcedure"></a> Using Transact-SQL
6363

‎docs/2014/relational-databases/user-defined-functions/delete-user-defined-functions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ manager: craigg
6262
5. In the **Delete Object** dialog box, click **OK**.
6363

6464
> [!IMPORTANT]
65-
> Click **Show Dependencies** in the **Delete Object** dialog box to open the *function_name***Dependencies** dialog box. This will show all of the objects that depend on the function and all of the objects on which the function depends.
65+
> Click **Show Dependencies** in the **Delete Object** dialog box to open the _function_name_**Dependencies** dialog box. This will show all of the objects that depend on the function and all of the objects on which the function depends.
6666
6767
## <a name="TsqlProcedure"></a> Using Transact-SQL
6868

‎docs/2014/relational-databases/views/delete-views.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ manager: craigg
4545
3. In the **Delete Object** dialog box, click **OK**.
4646

4747
> [!IMPORTANT]
48-
> Click **Show Dependencies** in the **Delete Object** dialog box to open the *view_name***Dependencies** dialog box. This will show all of the objects that depend on the view and all of the objects on which the view depends.
48+
> Click **Show Dependencies** in the **Delete Object** dialog box to open the _view_name_**Dependencies** dialog box. This will show all of the objects that depend on the view and all of the objects on which the view depends.
4949
5050
## <a name="TsqlProcedure"></a> Using Transact-SQL
5151

‎docs/2014/ssms/agent/define-the-response-to-an-alert-sql-server-management-studio.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,9 +59,9 @@ manager: craigg
5959

6060
4. Right-click the alert on which you want to define a response and select **Properties**.
6161

62-
5. In the *alert_name***alert properties** dialog box, under **Select a page**, select **Response**.
62+
5. In the _alert_name_**alert properties** dialog box, under **Select a page**, select **Response**.
6363

64-
6. Select the **Execute job** check box and, from the list below the **Execute job** check box, select a job to execute when the alert occurs. You can create a new job by clicking **New Job**. You can view more information about the job by clicking **View Job**. For more information about the available options in the **New Job** and **Job Properties***job_name* dialog boxes, see [Create a Job](create-a-job.md) and [View a Job](view-a-job.md).
64+
6. Select the **Execute job** check box and, from the list below the **Execute job** check box, select a job to execute when the alert occurs. You can create a new job by clicking **New Job**. You can view more information about the job by clicking **View Job**. For more information about the available options in the **New Job** and **Job Properties**_job_name_ dialog boxes, see [Create a Job](create-a-job.md) and [View a Job](view-a-job.md).
6565

6666
7. Select the **Notify Operators** check box if you want to notify operators when the alert is activated. In the **Operator list**, select one or more of the following methods for notifying the operator or operators: **E-mail**, **Pager**, or **Net Send**. You can create a new operator by clicking **New Operator**. You can view more information about an operator by clicking **View Operator**. For more information about the available options in the **New Operator** and **View Operator Properties** dialog boxes, see [Create an Operator](create-an-operator.md) and [View Information About an Operator](view-information-about-an-operator.md).
6767

‎docs/2014/ssms/agent/delete-a-job-category.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ manager: craigg
4444

4545
3. Right-click the **Jobs** folder and select **Manage Job Categories**.
4646

47-
4. In the **Manage Job Categories***server_name* dialog box, select the job category to delete.
47+
4. In the **Manage Job Categories**_server_name_ dialog box, select the job category to delete.
4848

4949
5. Click **Delete**.
5050

5151
6. In the **Job Categories** dialog box, click **Yes**.
5252

53-
7. Close the **Manage Job Categories***server_name* dialog box.
53+
7. Close the **Manage Job Categories**_server_name_ dialog box.
5454

5555

5656

‎docs/2014/ssms/agent/delete-a-sql-server-agent-proxy.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ manager: craigg
3636

3737
### <a name="Restrictions"></a> Limitations and Restrictions
3838

39-
- When you delete a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent proxy account, make sure the proxy does not reference any active job steps. To check for any job steps that reference the proxy, right-click the proxy, select **Properties**, and then, in the *proxy_name***Proxy Account Properties** dialog box, select the **References** page. If you delete a proxy, you are given the option to reassign all job steps that use that proxy in the **Delete Object** dialog box.
39+
- When you delete a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent proxy account, make sure the proxy does not reference any active job steps. To check for any job steps that reference the proxy, right-click the proxy, select **Properties**, and then, in the _proxy_name_**Proxy Account Properties** dialog box, select the **References** page. If you delete a proxy, you are given the option to reassign all job steps that use that proxy in the **Delete Object** dialog box.
4040

4141
- [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent proxies use credentials to store information about Windows user accounts. The user specified in the credential must have "Log on as a batch job" permission on the computer on which [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is running.
4242

‎docs/analytics-platform-system/pdw-permissions.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The following list describes the default permissions:
5757

5858
- When a login is created by usings **CREATE LOGIN** statement, the login receives the **CONNECT SQL** permission allowing the login to connect to the SQL Server PDW.
5959

60-
- When a database user is created by using the **CREATE USER** statement, the user receives the **CONNECT ON DATABASE::***<database_name>* permission, allowing the login to connect to that database as a user.
60+
- When a database user is created by using the **CREATE USER** statement, the user receives the **CONNECT ON DATABASE::**_<database_name>_ permission, allowing the login to connect to that database as a user.
6161

6262
- All principals, including the PUBLIC role, have no explicit or implicit permissions by default because implicit permissions are inherited from explicit permissions. Therefore, when no explicit permissions are present, there can also be no implicit permissions.
6363

@@ -92,7 +92,7 @@ An *implicit permission* is a **GRANT** or **DENY** permission that a principal
9292

9393
- A principal can inherit a permission on a subordinate object (such as a table) if the principal has a permission on one of the objects parent scopes (such as the schema of the table or the permission on the entire database).
9494

95-
- A principal can inherit a permission by having a permission that includes a subordinate permission. For example the **ALTER ANY USER** permission includes the both the **CREATE USER** and the **ALTER ON USER::***<name>* permissions.
95+
- A principal can inherit a permission by having a permission that includes a subordinate permission. For example the **ALTER ANY USER** permission includes the both the **CREATE USER** and the **ALTER ON USER::**_<name>_ permissions.
9696

9797
### Determining Permissions When Performing Actions
9898
The process of determining which permission to assign to a principal is complex. The complexity occurs when determining implicit permissions because principals can be members of multiple roles and permissions can be passed through multiple levels in the role hierarchy.

‎docs/analytics-platform-system/power-the-aps-appliance-on-or-off.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Before powering off the appliance, you should end all activity on the appliance.
4242

4343
4. Connect to ***appliance_domain*-HST01** and login with the appliance domain administrator account.
4444

45-
5. Using the **Failover Cluster Manager** connect to the ***appliance_domain*-WFOHST01** cluster, if not automatically connected, and then in the Navigation pane, click **Roles**. In the **Roles** pane:
45+
5. Using the **Failover Cluster Manager** connect to the **_appliance_domain_-WFOHST01** cluster, if not automatically connected, and then in the Navigation pane, click **Roles**. In the **Roles** pane:
4646

4747
1. Multi-select all of the virtual machines. Right-click them, and select **Shut Down**.
4848

@@ -69,21 +69,21 @@ Before powering off the appliance, you should end all activity on the appliance.
6969

7070
3. Log in to ***appliance_domain*-HST01** as the appliance domain administrator.
7171

72-
4. Start the **Hyper-V Manager** program (**virtmgmt.msc**) and connect to ***appliance_domain*-HST01** if not connected by default.
72+
4. Start the **Hyper-V Manager** program (**virtmgmt.msc**) and connect to **_appliance_domain_-HST01** if not connected by default.
7373

7474
1. If you cannot connect by name because the ***PDW_region*-AD01** is not running, try connecting by using the IP address.
7575

76-
2. In the **Virtual Machines** pane, locate ***PDW_region*-AD01** and confirm that it is running. If not, start this VM and wait for it to be fully started.
76+
2. In the **Virtual Machines** pane, locate **_PDW_region_-AD01** and confirm that it is running. If not, start this VM and wait for it to be fully started.
7777

7878
5. Power on the rest of the servers in the appliance.
7979

8080
6. While on **HST01** logged on as the appliance domain administrator, from **Hyper-V Manager**:
8181

8282
1. Connect to ***appliance_domain*-HST02**.
8383

84-
2. In the **Virtual Machines** pane, locate ***PDW_region*-AD02** and confirm that it is running. If not, start this VM and wait for it to be fully started.
84+
2. In the **Virtual Machines** pane, locate **_PDW_region_-AD02** and confirm that it is running. If not, start this VM and wait for it to be fully started.
8585

86-
7. Using the **Failover Cluster Manager** connect to the ***appliance_domain*-WFOHST01** cluster, if not automatically connected, and then in the **Navigation** pane, click **Roles**. In the **Roles** pane:
86+
7. Using the **Failover Cluster Manager** connect to the **_appliance_domain_-WFOHST01** cluster, if not automatically connected, and then in the **Navigation** pane, click **Roles**. In the **Roles** pane:
8787

8888
1. Multi-select all of the virtual machines, right-click them, and then click **Start**.
8989

‎docs/database-engine/availability-groups/windows/replicate-track-change-data-capture-always-on-availability.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ If Change Data Capture needs to be disabled on a database which is part of an Al
201201

202202
|||||
203203
|-|-|-|-|
204-
||**Publisher**|**Distributor***\*|**Subscriber**|
204+
||**Publisher**|**Distributor**_\_|**Subscriber**|
205205
|**Transactional**|Yes<br /><br /> Note: Does not include support for bi-directional and reciprocal transactional replication.|Yes|Yes|
206206
|**P2P**|No|No|No|
207207
|**Merge**|Yes|No|No|

0 commit comments

Comments
 (0)