Merge pull request #8584 from Saisang/sai-fixMultipleAsterisk-1218-1

fix multiple asterisk 3rd batch part 1

Author: Jak-MS

docs/2014/database-engine/availability-groups/windows/troubleshoot-always-on-availability-groups-configuration-sql-server.md

@@ -130,7 +130,7 @@ manager: craigg
 |![Checkbox](../../media/checkboxemptycenterxtraspacetopandright.gif "Checkbox")|Current primary replica|Ensure that the READ_ONLY_ROUTING_LIST contains only server instances that are hosting a readable secondary replica.|**To identify readable secondary replicas:** sys.availability_replicas  (**secondary_role_allow_connections_desc** column)<br /><br /> **To view a read-only routing list:** sys.availability_read_only_routing_lists<br /><br /> **To change a read-only routing list:** ALTER AVAILABILITY GROUP|[sys.availability_replicas &#40;Transact-SQL&#41;](/sql/relational-databases/system-catalog-views/sys-availability-replicas-transact-sql)<br /><br /> [sys.availability_read_only_routing_lists &#40;Transact-SQL&#41;](/sql/relational-databases/system-catalog-views/sys-availability-read-only-routing-lists-transact-sql)<br /><br /> [ALTER AVAILABILITY GROUP &#40;Transact-SQL&#41;](/sql/t-sql/statements/alter-availability-group-transact-sql)|  
 |![Checkbox](../../media/checkboxemptycenterxtraspacetopandright.gif "Checkbox")|Every replica in the read_only_routing_list|Ensure that the Windows firewall is not blocking the READ_ONLY_ROUTING_URL port.|-|[Configure a Windows Firewall for Database Engine Access](../../configure-windows/configure-a-windows-firewall-for-database-engine-access.md)|  
 |![Checkbox](../../media/checkboxemptycenterxtraspacetopandright.gif "Checkbox")|Every replica in the read_only_routing_list|In [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager, verify that:<br /><br /> SQL Server remote connectivity is enabled.<br /><br /> TCP/IP is enabled.<br /><br /> The IP addresses are configured correctly.|-|[View or Change Server Properties &#40;SQL Server&#41;](../../configure-windows/view-or-change-server-properties-sql-server.md)<br /><br /> [Configure a Server to Listen on a Specific TCP Port &#40;SQL Server Configuration Manager&#41;](../../configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port.md)|  
-|![Checkbox](../../media/checkboxemptycenterxtraspacetopandright.gif "Checkbox")|Every replica in the read_only_routing_list|Ensure that the READ_ONLY_ROUTING_URL (TCP**://*`system-address`*:***port*) contains the correct fully-qualified domain name (FQDN) and port number.|-|[Calculating read_only_routing_url for AlwaysOn](https://blogs.msdn.com/b/mattn/archive/2012/04/25/calculating-read-only-routing-url-for-alwayson.aspx)<br /><br /> [sys.availability_replicas &#40;Transact-SQL&#41;](/sql/relational-databases/system-catalog-views/sys-availability-replicas-transact-sql)<br /><br /> [ALTER AVAILABILITY GROUP &#40;Transact-SQL&#41;](/sql/t-sql/statements/alter-availability-group-transact-sql)|  
+|![Checkbox](../../media/checkboxemptycenterxtraspacetopandright.gif "Checkbox")|Every replica in the read_only_routing_list|Ensure that the READ_ONLY_ROUTING_URL (TCP<strong>://*`system-address`*:</strong>*port*) contains the correct fully-qualified domain name (FQDN) and port number.|-|[Calculating read_only_routing_url for AlwaysOn](https://blogs.msdn.com/b/mattn/archive/2012/04/25/calculating-read-only-routing-url-for-alwayson.aspx)<br /><br /> [sys.availability_replicas &#40;Transact-SQL&#41;](/sql/relational-databases/system-catalog-views/sys-availability-replicas-transact-sql)<br /><br /> [ALTER AVAILABILITY GROUP &#40;Transact-SQL&#41;](/sql/t-sql/statements/alter-availability-group-transact-sql)|  
 |![Checkbox](../../media/checkboxemptycenterxtraspacetopandright.gif "Checkbox")|Client system|Verify that the client driver supports read-only routing.|-|[AlwaysOn Client Connectivity (SQL Server)](always-on-client-connectivity-sql-server.md)|  
   
 ##  <a name="RelatedTasks"></a> Related Tasks  

docs/2014/relational-databases/collations/write-international-transact-sql-statements.md

@@ -30,11 +30,11 @@ manager: craigg
 
     -   ADO, OLE DB, and ODBC applications should use the ODBC timestamp, date, and time escape clauses of:  
 
-         **{ ts'**yyyy**-***mm***-***dd**hh***:***mm***:***ss*[**.***fff*] **'}** such as: **{ ts'**1998**-**09**-**24 10**:**02**:**20**' }**  
+         **{ ts'**yyyy**-**_mm_**-**_ddhh_**:**_mm_**:**_ss_[**.**_fff_] **'}** such as: **{ ts'**1998**-**09**-**24 10**:**02**:**20**' }**  
 
-         **{ d'** *yyyy* **-** *mm* **-** *dd* **'}** such as: **{ d'**1998**-**09**-**24**'}**  
+         **{ d'** _yyyy_ **-** _mm_ **-** _dd_ **'}** such as: **{ d'**1998**-**09**-**24**'}**  
 
-         **{ t'** *hh* **:** *mm* **:** *ss* **'}** such as: **{ t'**10:02:20**'}**  
+         **{ t'** _hh_ **:** _mm_ **:** _ss_ **'}** such as: **{ t'**10:02:20**'}**  
 
     -   Applications that use other APIs, or [!INCLUDE[tsql](../../includes/tsql-md.md)] scripts, stored procedures, and triggers, should use the unseparated numeric strings. For example, *yyyymmdd* as 19980924.  
 

docs/2014/relational-databases/data-collection/system-data-collection-set-reports.md

@@ -50,7 +50,7 @@ manager: craigg
  The table below the graph lists data collection times and corresponding usage data.  
 
 #### Disk Usage for Database: <database_name> Subreport  
- The **Disk usage for database:***<database_name>* subreport is displayed when you click a database name in the summary table of the Disk Usage Collection Set report. This report provides a numerical and graphical breakdown of space usage by the data and transaction log files of the database. Space usage for data files is categorized as a percentage allocated to index pages, unallocated space, data pages, and unused space. These categories are defined as follows:  
+ The **Disk usage for database:**_<database_name>_ subreport is displayed when you click a database name in the summary table of the Disk Usage Collection Set report. This report provides a numerical and graphical breakdown of space usage by the data and transaction log files of the database. Space usage for data files is categorized as a percentage allocated to index pages, unallocated space, data pages, and unused space. These categories are defined as follows:  
 
 |Category|Definition|  
 |--------------|----------------|  

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

@@ -82,7 +82,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)] statement:  
   

docs/2014/relational-databases/native-client/applications/using-connection-string-keywords-with-sql-server-native-client.md

@@ -71,7 +71,7 @@ manager: craigg
 |`QuotedId`|When "yes", QUOTED_IDENTIFIERS is set ON for the connection, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] uses the ISO rules regarding the use of quotation marks in SQL statements. When no, QUOTED_IDENTIFIERS is set OFF for the connection. [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] then follows the legacy [!INCLUDE[tsql](../../../includes/tsql-md.md)] rules regarding the use of quotation marks in SQL statements. For more information, see [Effects of ISO Options](../../native-client-odbc-queries/executing-statements/effects-of-iso-options.md).|  
 |`Regional`|When "yes", the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver uses client settings when converting currency, date, and time data to character data. The conversion is one way only; the driver does not recognize non-ODBC standard formats for date strings or currency values within; for example, a parameter used in an INSERT or UPDATE statement. When "no", the driver uses ODBC standard strings to represent currency, date, and time data that is converted to character data.|  
 |`SaveFile`|Name of an ODBC data source file into which the attributes of the current connection are saved if the connection is successful.|  
-|`Server`|The name of a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance. The value must be either the name of a server on the network, an IP address, or the name of a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager alias.<br /><br /> The `Address` keyword overrides the `Server` keyword.<br /><br /> You can connect to the default instance on the local server by specifying one of the following:<br /><br /> -   `Server=;`<br />-   `Server=.;`<br />-   `Server=(local);`<br />-   `Server=(localhost);`<br />-   **Server=(localdb)\\** *instancename* `;`<br /><br /> For more information about LocalDB support, see [SQL Server Native Client Support for LocalDB](../features/sql-server-native-client-support-for-localdb.md).<br /><br /> To specify a named instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], append **\\***InstanceName*.<br /><br /> When no server is specified, a connection is made to the default instance on the local computer.<br /><br /> If you specify an IP address, make sure that the TCP/IP or named pipes protocols are enabled in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager.<br /><br /> The complete syntax for the `Server` keyword is as follows:<br /><br /> `Server=`[*protocol*`:`]*Server*[`,`*port*]<br /><br /> *protocol* can be `tcp` (TCP/IP), `lpc` (shared memory), or `np` (named pipes).<br /><br /> The following is an example of specifying a named pipe:<br /><br /> `np:\\.\pipe\MSSQL$MYINST01\sql\query`<br /><br /> This line specifies named pipe protocol, a named pipe on the local machine (`\\.\pipe`), the name of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance (`MSSQL$MYINST01`), and the default name of the named pipe (`sql/query`).<br /><br /> If neither a *protocol* nor the `Network` keyword is specified, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client will use the protocol order specified in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager.<br /><br /> *port* is the port to connect to, on the specified server. By default, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] uses port 1433.<br /><br /> Spaces are ignored at the beginning of the value passed to `Server` in ODBC connection strings when using [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client.|  
+|`Server`|The name of a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance. The value must be either the name of a server on the network, an IP address, or the name of a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager alias.<br /><br /> The `Address` keyword overrides the `Server` keyword.<br /><br /> You can connect to the default instance on the local server by specifying one of the following:<br /><br /> -   `Server=;`<br />-   `Server=.;`<br />-   `Server=(local);`<br />-   `Server=(localhost);`<br />-   **Server=(localdb)\\** _instancename_ `;`<br /><br /> For more information about LocalDB support, see [SQL Server Native Client Support for LocalDB](../features/sql-server-native-client-support-for-localdb.md).<br /><br /> To specify a named instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], append **\\**_InstanceName_.<br /><br /> When no server is specified, a connection is made to the default instance on the local computer.<br /><br /> If you specify an IP address, make sure that the TCP/IP or named pipes protocols are enabled in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager.<br /><br /> The complete syntax for the `Server` keyword is as follows:<br /><br /> `Server=`[*protocol*`:`]*Server*[`,`*port*]<br /><br /> *protocol* can be `tcp` (TCP/IP), `lpc` (shared memory), or `np` (named pipes).<br /><br /> The following is an example of specifying a named pipe:<br /><br /> `np:\\.\pipe\MSSQL$MYINST01\sql\query`<br /><br /> This line specifies named pipe protocol, a named pipe on the local machine (`\\.\pipe`), the name of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] instance (`MSSQL$MYINST01`), and the default name of the named pipe (`sql/query`).<br /><br /> If neither a *protocol* nor the `Network` keyword is specified, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client will use the protocol order specified in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Configuration Manager.<br /><br /> *port* is the port to connect to, on the specified server. By default, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] uses port 1433.<br /><br /> Spaces are ignored at the beginning of the value passed to `Server` in ODBC connection strings when using [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client.|  
 |`ServerSPN`|The SPN for the server. The default value is an empty string. An empty string causes [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client to use the default, driver-generated SPN.|  
 |`StatsLog_On`|When "yes", enables the capture of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver performance data. When "no", [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver performance data is not available on the connection.|  
 |`StatsLogFile`|Full path and file name of a file used to record [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver performance statistics.|  

docs/2014/relational-databases/native-client/odbc/using-catalog-functions.md

@@ -37,7 +37,7 @@ manager: craigg
 
      Returns a list of the catalogs contained in a linked server.  
 
- After you have a linked server name and a catalog name, the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver supports getting information from the catalog by using a two-part name of *linked_server_name***.***catalog* for *CatalogName* on the following ODBC catalog functions:  
+ After you have a linked server name and a catalog name, the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver supports getting information from the catalog by using a two-part name of _linked_server_name_**.**_catalog_ for *CatalogName* on the following ODBC catalog functions:  
 
 -   **SQLColumnPrivileges**  
 
@@ -51,7 +51,7 @@ manager: craigg
 
 -   **SQLTables**  
 
- The two-part *linked_server_name***.***catalog* is also supported for *FKCatalogName* and *PKCatalogName* on [SQLForeignKeys](../../native-client-odbc-api/sqlforeignkeys.md).  
+ The two-part _linked_server_name_**.**_catalog_ is also supported for *FKCatalogName* and *PKCatalogName* on [SQLForeignKeys](../../native-client-odbc-api/sqlforeignkeys.md).  
 
  Using SQLLinkedServers and SQLLinkedCatalogs requires the following files:  
 

docs/2014/relational-databases/performance-monitor/use-sql-server-objects.md

@@ -34,7 +34,7 @@ manager: craigg
 # Use SQL Server Objects
   Microsoft [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides objects and counters that can be used by System Monitor to monitor activity in computers running an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. An object is any [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] resource, such as a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] lock or Windows process. Each object contains one or more counters that determine various aspects of the objects to monitor. For example, the **SQL Server Locks** object contains counters called **Number of Deadlocks/sec** and **Lock Timeouts/sec**.  
 
- Some objects have several instances if multiple resources of a given type exist on the computer. For example, the **Processor** object type will have multiple instances if a system has multiple processors. The **Databases** object type has one instance for each database on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Some object types (for example, the **Memory Manager** object) have only one instance. If an object type has multiple instances, you can add counters to track statistics for each instance, or in many cases, all instances at once. Counters for the default instance appear in the format **SQLServer:***\<object name>*. Counters for named instances appear in the format **MSSQL$***\<instance name>***:***\<counter name>* or **SQLAgent$***\<instance name>***:***\<counter name>*.  
+ Some objects have several instances if multiple resources of a given type exist on the computer. For example, the **Processor** object type will have multiple instances if a system has multiple processors. The **Databases** object type has one instance for each database on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Some object types (for example, the **Memory Manager** object) have only one instance. If an object type has multiple instances, you can add counters to track statistics for each instance, or in many cases, all instances at once. Counters for the default instance appear in the format **SQLServer:**_\<object name>_. Counters for named instances appear in the format **MSSQL$**_\<instance name>_**:**_\<counter name>_ or **SQLAgent$**_\<instance name>_**:**_\<counter name>_.  
 
  By adding or removing counters to the chart and saving the chart settings, you can specify the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] objects and counters that are monitored when System Monitor is started.  
 

docs/2014/relational-databases/performance/view-the-windows-application-log-windows-10.md

@@ -29,7 +29,7 @@ manager: craigg
 
 2.  In Event Viewer, click **Application**.  
 
-3.  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] events are identified by the entry **MSSQLSERVER** (named instances are identified with **MSSQL$***<instance_name>*) in the **Source** column. SQL Server Agent events are identified by the entry SQLSERVERAGENT (for named instances of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent events are identified with **SQLAgent$**\<*instance_name*>). Microsoft Search service events are identified by the entry **Microsoft Search**.  
+3.  [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] events are identified by the entry **MSSQLSERVER** (named instances are identified with **MSSQL$**_<instance_name>_) in the **Source** column. SQL Server Agent events are identified by the entry SQLSERVERAGENT (for named instances of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent events are identified with **SQLAgent$**\<*instance_name*>). Microsoft Search service events are identified by the entry **Microsoft Search**.  
 
 4.  To view the log of a different computer, right-click **Event Viewer**, click **Connect to another computer,** and complete the **Select Computer**dialog box.