Merge pull request #8586 from Saisang/sai-fixMultipleAsterisk-1218-3

fix multiple asterisk 3rd batch part 3

Author: Jak-MS

docs/2014/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections.md

@@ -65,7 +65,7 @@ SELECT auth_scheme FROM sys.dm_exec_connections WHERE session_id = @@spid ;
 
  **Named instance**  
 
--   *MSSQLSvc/FQDN*:[*port***|***instancename*], where:  
+-   *MSSQLSvc/FQDN*:[_port_**|**_instancename_], where:  
 
     -   *MSSQLSvc* is the service that is being registered.  
 
@@ -77,7 +77,7 @@ SELECT auth_scheme FROM sys.dm_exec_connections WHERE session_id = @@spid ;
 
  **Default instance**  
 
--   *MSSQLSvc/FQDN*:*port***|***MSSQLSvc/FQDN*, where:  
+-   *MSSQLSvc/FQDN*:_port_**|**_MSSQLSvc/FQDN_, where:  
 
     -   *MSSQLSvc* is the service that is being registered.  
 

docs/2014/database-engine/configure-windows/remote-servers.md

@@ -51,7 +51,7 @@ manager: craigg
 >  When possible, use Windows Authentication.  
   
 ### Remote Server Security Example  
- Consider these [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] installations: **serverSend** and **serverReceive**. **serverReceive** is configured to map an incoming login from **serverSend**, called **Sales_Mary**, to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] authenticated login in **serverReceive**, called **Alice**. Another incoming login from **serverSend**, called **Joe**, is mapped to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] authenticated login in **serverReceive***,* called **Joe**.  
+ Consider these [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] installations: **serverSend** and **serverReceive**. **serverReceive** is configured to map an incoming login from **serverSend**, called **Sales_Mary**, to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] authenticated login in **serverReceive**, called **Alice**. Another incoming login from **serverSend**, called **Joe**, is mapped to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] authenticated login in **serverReceive**_,_ called **Joe**.  
 
  The following Transact-SQL code example configures `serverSend` to perform RPCs against `serverReceive`.  
 

docs/2014/database-engine/configure-windows/run-sql-server-with-or-without-a-network.md

@@ -43,8 +43,8 @@ manager: craigg
 
  When connecting to an instance of a stand-alone [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from a local client such as **sqlcmd**, you bypass the network and connect directly to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using a local pipe. The difference between a local pipe and a network pipe is whether you are using a network. Both local and network pipes establish a connection with an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] by using the standard pipe (\\\\.\pipe\sql\query), unless otherwise directed.  
 
- When you connect to an instance of a local [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] without specifying a server name, you are using a local pipe. When you connect to an instance of a local [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and specify a server name explicitly, you are using either a network pipe or another network interprocess communication (IPC) mechanism, such as Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) (assuming you have configured [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to use multiple networks). Because a stand-alone [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] does not support network pipes, you must omit the unnecessary **/***<Server_name>* argument when connecting to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from a client. For example, to connect to a stand-alone instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from **osql**, type:  
+ When you connect to an instance of a local [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] without specifying a server name, you are using a local pipe. When you connect to an instance of a local [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and specify a server name explicitly, you are using either a network pipe or another network interprocess communication (IPC) mechanism, such as Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) (assuming you have configured [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to use multiple networks). Because a stand-alone [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] does not support network pipes, you must omit the unnecessary **/**_<Server_name>_ argument when connecting to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from a client. For example, to connect to a stand-alone instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] from **osql**, type:  
 
- **osql /Usa /P** *\<saPassword>*  
+ **osql /Usa /P** _\<saPassword>_  
 
 

docs/2014/database-engine/save-your-work-in-table-designer-visual-database-tools.md

@@ -22,7 +22,7 @@ manager: craigg
 
 1.  Click anywhere in the Table Designer.  
 
-2.  From the **File** menu, choose **Save***tablename*.  
+2.  From the **File** menu, choose **Save**_tablename_.  
 
 3.  In the **Save** dialog box, click **Yes** to update the database.  
 

docs/2014/relational-databases/backup-restore/recover-a-database-without-restoring-data-transact-sql.md

@@ -57,7 +57,7 @@ RESTORE DATABASE AdventureWorks2012
 
  The [RESTORE](/sql/t-sql/statements/restore-statements-transact-sql) syntax for a recovery-only file restore is:  
 
- RESTORE DATABASE *database_name* { FILE **=***logical_file_name* | FILEGROUP **=***logical_filegroup_name* }[ **,**...*n* ] WITH RECOVERY  
+ RESTORE DATABASE *database_name* { FILE **=**_logical_file_name_ | FILEGROUP **=**_logical_filegroup_name_ }[ **,**...*n* ] WITH RECOVERY  
 
  **Example**  
 

docs/2014/relational-databases/backup-restore/recover-to-a-log-sequence-number-sql-server.md

@@ -58,11 +58,11 @@ manager: craigg
 ## Transact-SQL Syntax for Restoring to an LSN  
  By using a [RESTORE](/sql/t-sql/statements/restore-statements-transact-sql) statement, you can stop at or immediately before the LSN, as follows:  
 
--   Use the WITH STOPATMARK **='**lsn:*<lsn_number>***'** clause, where lsn:*\<lsnNumber>* is a string that specifies that the log record that contains the specified LSN is the recovery point.  
+-   Use the WITH STOPATMARK **='**lsn:_<lsn_number>_**'** clause, where lsn:*\<lsnNumber>* is a string that specifies that the log record that contains the specified LSN is the recovery point.  
 
      STOPATMARK roll forwards to the LSN and includes that log record in the roll forward.  
 
--   Use the WITH STOPBEFOREMARK **='**lsn:*<lsn_number>***'** clause, where lsn:*\<lsnNumber>* is a string that specifies that the log record immediately before the log record that contains the specified LSN number is the recovery point.  
+-   Use the WITH STOPBEFOREMARK **='**lsn:_<lsn_number>_**'** clause, where lsn:*\<lsnNumber>* is a string that specifies that the log record immediately before the log record that contains the specified LSN number is the recovery point.  
 
      STOPBEFOREMARK rolls forward to the LSN and excludes that log record from the roll forward.  
 

docs/2014/relational-databases/backup-restore/restore-the-master-database-transact-sql.md

@@ -37,7 +37,7 @@ manager: craigg
  The following example restores the `master` database on the default server instance. The example assumes that the server instance is already running in single-user mode. The example starts `sqlcmd` and executes a `RESTORE DATABASE` statement that restores a full database backup of `master` from a disk device: `Z:\SQLServerBackups\master.bak`.  
 
 > [!NOTE]
->  For a named instance, the **sqlcmd** command must specify the **-S***\<ComputerName>*\\*\<InstanceName>* option.  
+>  For a named instance, the **sqlcmd** command must specify the **-S**_\<ComputerName>_\\*\<InstanceName>* option.  
   
 ```  
   

docs/2014/relational-databases/data-tier-applications/register-a-database-as-a-dac.md

@@ -95,7 +95,7 @@ manager: craigg
  **Cancel** - Terminates the wizard without registering the DAC.  
 
 ### Validating Objects  
- **Checking**  *SchemaName* **.** *ObjectName* **.** - Displays a progress bar as the wizard verifies the dependencies of the retrieved objects, and verifies that they are all valid objects for a DAC. *SchemaName***.***ObjectName* identify which object is currently being verified.  
+ **Checking**  _SchemaName_ **.** _ObjectName_ **.** - Displays a progress bar as the wizard verifies the dependencies of the retrieved objects, and verifies that they are all valid objects for a DAC. _SchemaName_**.**_ObjectName_ identify which object is currently being verified.  
 
  **\< Previous** - Returns you to the **Set Properties** page to change your entries.  
 

docs/2014/relational-databases/databases/revert-a-database-to-a-database-snapshot.md

@@ -93,7 +93,7 @@ manager: craigg
 
      A revert operation requires RESTORE DATABASE permissions on the source database. To revert the database, use the following Transact-SQL statement:  
 
-     RESTORE DATABASE *database_name* FROM DATABASE_SNAPSHOT **=***database_snapshot_name*  
+     RESTORE DATABASE *database_name* FROM DATABASE_SNAPSHOT **=**_database_snapshot_name_  
 
      Where *database_name* is the source database and *database_snapshot_name* is the name of the snapshot to which you want to revert the database. Notice that in this statement, you must specify a snapshot name rather than a backup device.  
 

docs/2014/relational-databases/indexes/rename-indexes.md

@@ -60,7 +60,7 @@ manager: craigg
 
 7.  Click **Close**.  
 
-8.  On the **File** menu, click **Save***table_name*.  
+8.  On the **File** menu, click **Save**_table_name_.  
 
 #### To rename an index by using Object Explorer