Merge pull request #7658 from v-alje/bulk-fix-more-asterisks

Fixing triple asterisks for LOC

Author: MightyPen

docs/2014/database-engine/availability-groups/windows/overview-of-powershell-cmdlets-for-always-on-availability-groups-sql-server.md

@@ -54,7 +54,7 @@ manager: craigg
 |Cmdlets|Description|Supported on|  
 |-------------|-----------------|------------------|  
 |`Backup-SqlDatabase`|Creates a data or log backup.|Any online database (for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)], a database on the server instance that hosts the primary replica)|  
-|`Restore-SqlDatabase`|Restores a backup.|Any instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] (for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)], a server instance that hosts a secondary replica)<br /><br /> **\*\* Important \*\*** When preparing a secondary database, you must use the `-NoRecovery` parameter in every `Restore-SqlDatabase` command.|  
+|`Restore-SqlDatabase`|Restores a backup.|Any instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] (for [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)], a server instance that hosts a secondary replica)<br /><br /> **&#42;&#42; Important &#42;&#42;** When preparing a secondary database, you must use the `-NoRecovery` parameter in every `Restore-SqlDatabase` command.|  
 
  For information about using these cmdlets to prepare a secondary database, see [Manually Prepare a Secondary Database for an Availability Group &#40;SQL Server&#41;](manually-prepare-a-secondary-database-for-an-availability-group-sql-server.md).  
 

docs/2014/integration-services/packages/execute-package-utility-dtexecui-ui-reference.md

@@ -277,7 +277,7 @@ manager: craigg
  Click to close the **Execute Package Utility** dialog box.  
 
 ## Logging Page  
- Use the **Logging** page of the **Execute Package Utility** dialog box to make log providers available to the package at run time. Provide the package log provider type and the connection string for connecting to the log. Each log provider entry adds a **/LOGGER***classid* option to the command prompt.  
+ Use the **Logging** page of the **Execute Package Utility** dialog box to make log providers available to the package at run time. Provide the package log provider type and the connection string for connecting to the log. Each log provider entry adds a **/LOGGER**_classid_ option to the command prompt.  
 
 ### Options  
  **Log Provider**  
@@ -296,7 +296,7 @@ manager: craigg
  Click to close the **Execute Package Utility** dialog box.  
 
 ## Set Values Page  
- Use the **Set Values** page of the **Execute Package Utility** dialog box to set the property values of packages, executables, connections, variables, and log providers by typing the paths of properties and the property values. Each path entry adds a **/SET***propertypath;value* option to the command prompt.  
+ Use the **Set Values** page of the **Execute Package Utility** dialog box to set the property values of packages, executables, connections, variables, and log providers by typing the paths of properties and the property values. Each path entry adds a **/SET**_propertypath;value_ option to the command prompt.  
 
 ### Options  
  **Property Path**  

docs/2014/integration-services/schedule-a-package-by-using-sql-server-agent.md

@@ -64,8 +64,8 @@ manager: craigg
     |---------|-------------|  
     |**Package**|**Server**<br /><br /> Type or select the name of the database server instance that hosts the SSISDB catalog.<br /><br /> When **SSIS Catalog** is the package source, you can log on to the server using only a Microsoft Windows user account. [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] authentication is not available.|  
     ||**Package**<br /><br /> Click the ellipsis button and select a package.<br /><br /> You are selecting a package in a folder under the **Integration Services Catalogs** node in **Object Explorer**.|  
-    |**Parameters**<br /><br /> Located on the **Configuration** tab.|Enter new values for parameters that are contained in the package. You can enter a literal value or use the value contained in a server environment variable that you have already mapped to the parameter.  **\*\* Important \*\*** If you have mapped multiple parameters and/or connection manager properties to variables contained in multiple environments, [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Agent displays an error message. For a given execution, a package can execute only with the values contained in a single server environment.<br /><br /> To enter the literal value, click the ellipsis button next to a parameter. The **Edit Literal Value for Execution** dialog box appears.<br /><br /> To use an environment variable, click **Environment** and then select the environment that contains the variable you want to use.<br /><br /> <br /><br /> The **Parameters** tab displays parameters that you added when you designed the package, for example by using [!INCLUDE[ssBIDevStudioFull](../includes/ssbidevstudiofull-md.md)]. The tab also displays parameters that were added to the package when you converted the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] project from the package deployment model to the project deployment model. The **Integration Services Project Conversion Wizard** enables you to replace package configurations with parameters.<br /><br /> For information on how to create a server environment and map a variable to a parameter, see [Create and Map a Server Environment](../../2014/integration-services/create-and-map-a-server-environment.md).|  
-    |**Connection Managers**<br /><br /> Located on the **Configuration** tab.|Change values for connection manager properties. For example, you can change the server name.<br /><br /> Parameters are automatically generated on the SSIS server for the connection manager properties.<br /><br /> To change a property value, you can enter a literal value or use the value contained in a server environment variable that you have already mapped to the connection manager property. **\*\* Important \*\*** If you have mapped multiple parameters and/or connection manager properties to variables contained in multiple environments, [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Agent displays an error message. For a given execution, a package can execute only with the values contained in a single server environment.<br /><br /> To enter the literal value, click the ellipsis button next to a parameter. The **Edit Literal Value for Execution** dialog box appears.<br /><br /> To use an environment variable, click **Environment** and then select the environment that contains the variable you want to use.<br /><br /> <br /><br /> For information on how to create a server environment and map a variable to a connection manager property, see [Create and Map a Server Environment](../../2014/integration-services/create-and-map-a-server-environment.md).|  
+    |**Parameters**<br /><br /> Located on the **Configuration** tab.|Enter new values for parameters that are contained in the package. You can enter a literal value or use the value contained in a server environment variable that you have already mapped to the parameter.  **&#42;&#42; Important &#42;&#42;** If you have mapped multiple parameters and/or connection manager properties to variables contained in multiple environments, [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Agent displays an error message. For a given execution, a package can execute only with the values contained in a single server environment.<br /><br /> To enter the literal value, click the ellipsis button next to a parameter. The **Edit Literal Value for Execution** dialog box appears.<br /><br /> To use an environment variable, click **Environment** and then select the environment that contains the variable you want to use.<br /><br /> <br /><br /> The **Parameters** tab displays parameters that you added when you designed the package, for example by using [!INCLUDE[ssBIDevStudioFull](../includes/ssbidevstudiofull-md.md)]. The tab also displays parameters that were added to the package when you converted the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] project from the package deployment model to the project deployment model. The **Integration Services Project Conversion Wizard** enables you to replace package configurations with parameters.<br /><br /> For information on how to create a server environment and map a variable to a parameter, see [Create and Map a Server Environment](../../2014/integration-services/create-and-map-a-server-environment.md).|  
+    |**Connection Managers**<br /><br /> Located on the **Configuration** tab.|Change values for connection manager properties. For example, you can change the server name.<br /><br /> Parameters are automatically generated on the SSIS server for the connection manager properties.<br /><br /> To change a property value, you can enter a literal value or use the value contained in a server environment variable that you have already mapped to the connection manager property. **&#42;&#42; Important &#42;&#42;** If you have mapped multiple parameters and/or connection manager properties to variables contained in multiple environments, [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] Agent displays an error message. For a given execution, a package can execute only with the values contained in a single server environment.<br /><br /> To enter the literal value, click the ellipsis button next to a parameter. The **Edit Literal Value for Execution** dialog box appears.<br /><br /> To use an environment variable, click **Environment** and then select the environment that contains the variable you want to use.<br /><br /> <br /><br /> For information on how to create a server environment and map a variable to a connection manager property, see [Create and Map a Server Environment](../../2014/integration-services/create-and-map-a-server-environment.md).|  
     |**Advanced**<br /><br /> Located on the **Configuration** tab.|Configure the following additional settings for the package execution.<br /><br /> <br /><br /> **Property overrides**: Click **Add** to enter a new value for a package property, specify the property path, and indicate whether the property value is sensitive. The [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] server encrypts sensitive data. To edit or remove the settings for a property, click a row in the **Property** overrides box and then click **Edit** or **Remove**. Note that the **Property overrides** option is intended for packages with configurations that you upgraded from a previous release of [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)]. Packages that you create using [!INCLUDE[ssISCurrent](../includes/ssiscurrent-md.md)] and deploy to the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] server use parameters instead of configurations. You can find the property path by doing one of the following:<br /><br /> Copy the property path from the XML configuration file (\*.dtsconfig) file. The path is listed in the Configuration section of the file, as a value of the Path attribute. The following is an example of the path for the MaximumErrorCount property.<br /><br /> \Package.Properties[MaximumErrorCount]<br /><br /> Run the **Package Configuration Wizard** and copy the property paths from the final **Completing the Wizard** page. You can then cancel the wizard.|  
     ||**Logging level**: The logging level you select determines what information is displayed in SSISDB views and in reports for the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] server. Note that selecting the **Performance** or **Verbose** logging level may impact the performance of the package execution. Select one of the following logging levels for the package execution:<br /><br /> **None**: Logging is turned off. Only the package execution status is logged.<br /><br /> **Basic**: All events are logged, except custom and diagnostic events. This is the default value for the logging level.<br /><br /> **Performance**: Only performance statistics, and OnError and OnWarning events, are logged.<br /><br /> **Verbose**: All events are logged, including custom and diagnostic events.<br /><br /> For more information, see [Enable Logging for Package Execution on the SSIS Server](../../2014/integration-services/enable-logging-for-package-execution-on-the-ssis-server.md).|  
     ||**Dump on errors**: Specify whether debug dump files are generated when any error occurs during the execution of the package.<br /><br /> The files contain information about the execution of the package that can help you troubleshoot issues.<br /><br /> When you select this option, and an error occurs during execution, [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] creates a .mdmp file (binary file) and a .tmp file (text file). By default, [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] stores the files in the *\<drive>:*\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps folder.|  

docs/2014/relational-databases/maintenance-plans/job-activity-monitor-filter-settings.md

@@ -54,7 +54,7 @@ manager: craigg
  This unnamed box provides a short description of the criteria as they are selected.  
 
  **Apply filter**  
- To apply the filter, click **Apply****filter** and then click **OK**. To retain the filter settings in the **Filter****Settings** dialog box, but not apply them, uncheck **Apply****filter**, and then click **OK**, to display all rows.  
+ To apply the filter, click **Apply filter** and then click **OK**. To retain the filter settings in the **Filter Settings** dialog box, but not apply them, uncheck **Apply filter**, and then click **OK**, to display all rows.  
 
  **Clear**  
  Returns the filter settings back to the default settings.  

docs/2014/relational-databases/native-client-odbc-bulk-copy-operations/converting-from-db-library-to-odbc-bulk-copy.md

@@ -31,7 +31,7 @@ manager: craigg
   
 -   The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Native Client ODBC driver does not support DB-Library message and error handlers; you must call **SQLGetDiagRec** to get errors and messages raised by the ODBC bulk copy functions. The ODBC versions of bulk copy functions return the standard bulk copy return codes of SUCCEED or FAILED, not ODBC-style return codes, such as SQL_SUCCESS or SQL_ERROR.  
   
--   The values specified for the DB-Library [bcp_bind](../native-client-odbc-extensions-bulk-copy-functions/bcp-bind.md)*varlen* parameter are interpreted differently than the ODBC **bcp_bind***cbData* parameter.  
+-   The values specified for the DB-Library [bcp_bind](../native-client-odbc-extensions-bulk-copy-functions/bcp-bind.md)*varlen* parameter are interpreted differently than the ODBC **bcp_bind**_cbData_ parameter.  
   
     |Condition indicated|DB-Library *varlen* value|ODBC *cbData* value|  
     |-------------------------|--------------------------------|-------------------------|  
@@ -41,7 +41,7 @@ manager: craigg
   
      In DB-Library, a *varlen* value of -1 indicates that variable length data is being supplied, which in the ODBC *cbData* is interpreted to mean that only NULL values are being supplied. Change any DB-Library *varlen* specifications of -1 to SQL_VARLEN_DATA and any *varlen* specifications of 0 to SQL_NULL_DATA.  
   
--   The DB-Library **bcp_colfmt***file_collen* and the ODBC [bcp_colfmt](../native-client-odbc-extensions-bulk-copy-functions/bcp-colfmt.md)*cbUserData* have the same issue as the **bcp_bind***varlen* and *cbData* parameters noted above. Change any DB-Library *file_collen* specifications of -1 to SQL_VARLEN_DATA and any *file_collen* specifications of 0 to SQL_NULL_DATA.  
+-   The DB-Library **bcp\_colfmt**_file\_collen_ and the ODBC [bcp_colfmt](../native-client-odbc-extensions-bulk-copy-functions/bcp-colfmt.md)*cbUserData* have the same issue as the **bcp_bind**_varlen_ and *cbData* parameters noted above. Change any DB-Library *file_collen* specifications of -1 to SQL_VARLEN_DATA and any *file_collen* specifications of 0 to SQL_NULL_DATA.  
   
 -   The *iValue* parameter of the ODBC [bcp_control](../native-client-odbc-extensions-bulk-copy-functions/bcp-control.md) function is a void pointer. In DB-Library, *iValue* was an integer. Cast the values for the ODBC *iValue* to void *.  
   

docs/2014/relational-databases/tables/view-the-dependencies-of-a-table.md

@@ -47,7 +47,7 @@ manager: craigg
 
 2.  Right-click a table, and then click **View Dependencies**.  
 
-3.  In the **Object Dependencies***\<object name>* dialog box, select either **Objects that depend on** *\<object name>*, or **Objects on which***\<object name>***depends**.  
+3.  In the **Object Dependencies**_\<object name>_ dialog box, select either **Objects that depend on** *\<object name>*, or **Objects on which**_\<object name>_**depends**.  
 
 4.  Select an object in the **Dependencies** grid. The type of object (such as "Trigger" or "Stored Procedure"), appears in the **Type** box.