Merge pull request #8587 from Saisang/sai-fixMultipleAsterisk-1218-4

fix multiple asterisk 3rd batch part 4

Author: Jak-MS

docs/2014/analysis-services/instances/introduction-to-monitoring-analysis-services-with-sql-server-profiler.md

@@ -49,7 +49,7 @@ manager: craigg
 -   A trace can continue when [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] stops and restarts.  
 
     > [!NOTE]  
-    >  Passwords are not revealed in trace events, but are replaced by ****** in the event.  
+    >  Passwords are not revealed in trace events, but are replaced by \*\*\*\*\*\* in the event.  
   
  For optimal performance, use [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] to monitor only those events in which you are most interested. Monitoring too many events adds overhead and can cause the trace file or table to grow very large, especially when you monitor over a long period of time. In addition, use filtering to limit the amount of data that is collected and to prevent traces from becoming too large.  
 

docs/2014/database-engine/configure-windows/scm-services-prevent-automatic-startup-of-an-instance.md

@@ -31,9 +31,9 @@ manager: craigg
 
 3.  In the details pane, right-click **MSSQLServer**, and then click **Properties.**  
 
-4.  In the **SQL Server \<***instancename***> Properties** dialog box, in the **Properties** box, set the value of **Start Mode** to **Manual**.  
+4.  In the **SQL Server \<**_instancename_**> Properties** dialog box, in the **Properties** box, set the value of **Start Mode** to **Manual**.  
 
-5.  Click **OK** to close the **SQL Server \<***instancename***> Properties** dialog box, and then close [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager.  
+5.  Click **OK** to close the **SQL Server \<**_instancename_**> Properties** dialog box, and then close [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager.  
 
 ## See Also  
  [Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service](start-stop-pause-resume-restart-sql-server-services.md)  

docs/2014/database-engine/install-windows/install-sql-server-with-smb-fileshare-as-a-storage-option.md

@@ -92,11 +92,11 @@ manager: craigg
     > [!NOTE]  
     >  The FULL CONTROL share permissions and NTFS permissions on the SMB share folders should be restricted to: [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service account, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent service account and windows users with admin server roles.  
   
-     It is recommended to use domain account as a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service account. If system account is used as a service account, grant the permissions for the machine account in the format: *<domain_name>***\\***<computer_name>***$**.  
+     It is recommended to use domain account as a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] service account. If system account is used as a service account, grant the permissions for the machine account in the format: _<domain_name>_**\\**_<computer_name>_**$**.  
   
     > [!NOTE]  
     >  -   During [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] setup, it is required to specify domain account as a service account if SMB file share is specified as a storage option. With SMB file share, System account can only be specified as a service account post [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] installation.  
-    > -   Virtual accounts cannot be authenticated to a remote location. All virtual accounts use the permission of machine account. Provision the machine account in the format *<domain_name>***\\***<computer_name>***$**.  
+    > -   Virtual accounts cannot be authenticated to a remote location. All virtual accounts use the permission of machine account. Provision the machine account in the format _<domain_name>_**\\**_<computer_name>_**$**.  
   
 -   The account used to install [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] should have FULL CONTROL permissions on the SMB file share folder used as the data directory, or any other data folders (User database directory, user database log directory, TempDB directory, TempDB log directory, backup directory) during Cluster Setup.  
   

docs/2014/relational-databases/backup-restore/media-sets-media-families-and-backup-sets-sql-server.md

@@ -134,7 +134,7 @@ WITH
 
  ![Second backup set spread across 3 media-set tapes](../../database-engine/media/bnr-mediaset-appendedto.gif "Second backup set spread across 3 media-set tapes")  
 
- When you are restoring backups, you can use you the FILE option to specify which backups you want to use. The following example shows the use of FILE **=***backup_set_file_number* clauses when restoring a full database backup of the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] database followed by a differential database backup on the same media set. The media set uses three backup tapes, which are on tape drives `\\.\tape0`, `tape1`, and `tape2`.  
+ When you are restoring backups, you can use you the FILE option to specify which backups you want to use. The following example shows the use of FILE **=**_backup_set_file_number_ clauses when restoring a full database backup of the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] database followed by a differential database backup on the same media set. The media set uses three backup tapes, which are on tape drives `\\.\tape0`, `tape1`, and `tape2`.  
 
 ```  
 RESTORE DATABASE AdventureWorks2012 FROM TAPE = '\\.\tape0', TAPE = '\\.\tape1', TAPE = '\\.\tape2'  

docs/2014/relational-databases/databases/move-a-database-using-detach-and-attach-transact-sql.md

@@ -59,7 +59,7 @@ manager: craigg
     > [!IMPORTANT]  
     >  For a production database, place the database and transaction log on separate disks.  
   
-     To copy files over the network to a disk on a remote computer, use the universal naming convention (UNC) name of the remote location. A UNC name takes the form **\\\\***Servername***\\***Sharename***\\***Path***\\***Filename*. As with writing files to the local hard disk, the appropriate permissions that are required to read or write to a file on the remote disk must be granted to the user account used by the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
+     To copy files over the network to a disk on a remote computer, use the universal naming convention (UNC) name of the remote location. A UNC name takes the form **\\\\**_Servername_**\\**_Sharename_**\\**_Path_**\\**_Filename_. As with writing files to the local hard disk, the appropriate permissions that are required to read or write to a file on the remote disk must be granted to the user account used by the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
   
 3.  Attach the moved database and, optionally, its log by executing the following [!INCLUDE[tsql](../../includes/tsql-md.md)] statements:  
   

docs/2014/relational-databases/errors-events/mssqlserver-17832-database-engine-error.md

@@ -45,7 +45,7 @@ manager: craigg
 > [!CAUTION]  
 >  [!INCLUDE[ssNoteRegistry](../../includes/ssnoteregistry-md.md)]  
   
- **To change the MaxTokenSize**  **on the server computer**  
+ **To change the MaxTokenSize  on the server computer**  
 
 1.  On the **Start** menu, click **Run**.  
 

docs/2014/relational-databases/import-export/import-bulk-data-by-using-bulk-insert-or-openrowset-bulk-sql-server.md

@@ -96,7 +96,7 @@ manager: craigg
  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and [!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows can be configured to enable an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to connect to another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by forwarding the credentials of an authenticated Windows user. This arrangement is known as *impersonation* or *delegation*. Understanding how [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] version handle security for user impersonation is important when you use BULK INSERT or OPENROWSET. User impersonation allows the data file to reside on a different computer than either the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] process or the user. For example, if a user on **Computer_A** has access to a data file on **Computer_B**, and the delegation of credentials has been set appropriately, the user can connect to an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that is running on **Computer_C**, access the data file on **Computer_B**, and bulk import data from that file into a table on **Computer_C**.  
 
 ## Bulk Importing from a Remote Data File  
- To use BULK INSERT or INSERT...SELECT \* FROM OPENROWSET(BULK...) to bulk import data from another computer, the data file must be shared between the two computers. To specify a shared data file, use its universal naming convention (UNC) name, which takes the general form, **\\\\***Servername***\\***Sharename***\\***Path***\\***Filename*. Additionally, the account used to access the data file must have the permissions that are required for reading the file on the remote disk.  
+ To use BULK INSERT or INSERT...SELECT \* FROM OPENROWSET(BULK...) to bulk import data from another computer, the data file must be shared between the two computers. To specify a shared data file, use its universal naming convention (UNC) name, which takes the general form, **\\\\**_Servername_**\\**_Sharename_**\\**_Path_**\\**_Filename_. Additionally, the account used to access the data file must have the permissions that are required for reading the file on the remote disk.  
 
  For example, the following `BULK INSERT` statement bulk imports data into the `SalesOrderDetail` table of the `AdventureWorks` database from a data file that is named `newdata.txt`. This data file resides in a shared folder named `\dailyorders` on a network share directory named `salesforce` on a system named `computer2`.  
 

docs/2014/relational-databases/indexes/move-an-existing-index-to-a-different-filegroup.md

@@ -67,7 +67,7 @@ manager: craigg
 
 8.  Click **Close**.  
 
-9. On the **File** menu, select **Save***table_name*.  
+9. On the **File** menu, select **Save**_table_name_.  
 
 #### To move an existing index to a different filegroup in Object Explorer  
 
@@ -93,7 +93,7 @@ manager: craigg
 
 8.  Click **OK**.  
 
- The following information is available on the **Storage** page of the **Index Properties -** *index_name* dialog box:  
+ The following information is available on the **Storage** page of the **Index Properties -** _index_name_ dialog box:  
 
  **Filegroup**  
  Stores the index in the specified filegroup. The list only displays standard (row) filegroups. The default list selection is the PRIMARY filegroup of the database.  

docs/2014/relational-databases/lesson-2-connecting-from-another-computer.md

@@ -38,7 +38,7 @@ manager: craigg
     > [!NOTE]  
     >  You might have both 32 bit and 64 bit options available.  
   
-2.  In **SQL Server Configuration Manager**, expand **SQL Server Network Configuration**, and then click **Protocols for** *\<InstanceName>*.  
+2.  In **SQL Server Configuration Manager**, expand **SQL Server Network Configuration**, and then click **Protocols for** _\<InstanceName>_.  
 
      The default instance (an unnamed instance) is listed as **MSSQLSERVER**. If you installed a named instance, the name you provided is listed. [!INCLUDE[ssExpressEd11](../includes/ssexpressed11-md.md)] installs as **SQLEXPRESS**, unless you changed the name during setup.  
 
@@ -106,7 +106,7 @@ manager: craigg
 
 2.  In the **Connect to Server** dialog box, confirm **Database Engine** in the **Server type** box.  
 
-3.  In the **Server name** box, type **tcp:** to specify the protocol, followed by the computer name, a comma, and the port number. To connect to the default instance, the port 1433 is implied and can be omitted; therefore, type **tcp:***<computer_name>*. In our example for a named instance, type **tcp:***<computer_name>***,49172**.  
+3.  In the **Server name** box, type **tcp:** to specify the protocol, followed by the computer name, a comma, and the port number. To connect to the default instance, the port 1433 is implied and can be omitted; therefore, type **tcp:**_<computer_name>_. In our example for a named instance, type **tcp:**_<computer_name>_**,49172**.  
 
     > [!NOTE]  
     >  If you omit **tcp:** from the **Server name** box, then the client will attempt all protocols that are enabled, in the order specified in the client configuration.  

docs/2014/relational-databases/linked-servers/linked-servers-database-engine.md

@@ -72,7 +72,7 @@ manager: craigg
 
  You can also define linked servers by using [!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)]. In the Object Explorer, right-click **Server Objects**, select **New**, and select **Linked Server**. You can delete a linked server definition by right-clicking the linked server name and selecting **Delete**.  
 
- When you execute a distributed query against a linked server, include a fully qualified, four-part table name for each data source to query. This four-part name should be in the form *linked_server_name.catalog***.*`schema`*.***object_name*.  
+ When you execute a distributed query against a linked server, include a fully qualified, four-part table name for each data source to query. This four-part name should be in the form _linked_server_name.catalog_**._`schema`_.**_object_name_.  
 
 > [!NOTE]  
 >  Linked servers can be defined to point back (loop back) to the server on which they are defined. Loopback servers are most useful when testing an application that uses distributed queries on a single server network. Loopback linked servers are intended for testing and are not supported for many operations, such as distributed transactions.