Added titleSuffix while updating includes

Author: markingmyname

docs/ssms/scripting/edit-a-breakpoint-location.md

@@ -1,40 +1,46 @@
 ---
-title: "Edit a Breakpoint Location"
-ms.custom: ""
-ms.date: "03/14/2017"
+title: Edit a Breakpoint Location
+titleSuffix: T-SQL debugger
 ms.prod: sql
 ms.prod_service: "sql-tools"
 ms.technology: scripting
-ms.reviewer: ""
 ms.topic: conceptual
 helpviewer_keywords: 
   - "Transact-SQL debugger, breakpoint location"
 ms.assetid: 5c28e411-0377-4210-a7ce-2a5c13dcdf74
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
+ms.custom: ""
+ms.date: 12/04/2019
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
+
 # Edit a Breakpoint Location
-[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
-  The breakpoint location specifies the line and character where the breakpoint resides in a [!INCLUDE[tsql](../../includes/tsql-md.md)] script file. You can edit the breakpoint location to move the breakpoint to another location in the script, or to a different script.  
-  
-## Editing a Location  
- When you edit a breakpoint location, the breakpoint moves to the new location, carrying with it all of the existing properties, such as a hit count or condition.  
-  
-#### To Edit a Breakpoint Location  
-  
-1.  In the editor window, right-click the breakpoint glyph, and then click **Location** on the shortcut menu.  
+
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+
+The breakpoint location specifies the line and character where the breakpoint resides in a [!INCLUDE[tsql](../../includes/tsql-md.md)] script file. You can edit the breakpoint location to move the breakpoint to another location in the script, or to a different script.
+
+## Editing a Location
+
+When you edit a breakpoint location, the breakpoint moves to the new location, carrying with it all of the existing properties, such as a hit count or condition.  
+
+#### To Edit a Breakpoint Location
+
+1. In the editor window, right-click the breakpoint glyph, and then click **Location** on the shortcut menu.  
 
      -or-  
 
      In the **Breakpoints** window, right-click the breakpoint glyph, and then click **Location** on the shortcut menu.  
 
-2.  In the **File Breakpoint** dialog box, edit **File** to specify a new file, **Line** to specify a new line, or **Character** to specify a new location within the line. If the new file you specify is already open in a query editor window, the breakpoint is moved to that editor window. If the file is not opened, a new editor window is opened, the file is loaded in, and the breakpoint moved to the new location.  
+2. In the **File Breakpoint** dialog box, edit **File** to specify a new file, **Line** to specify a new line, or **Character** to specify a new location within the line. If the new file you specify is already open in a query editor window, the breakpoint is moved to that editor window. If the file is not opened, a new editor window is opened, the file is loaded in, and the breakpoint moved to the new location.  
 
      The **Allow the source code to be different from the original version** option has no effect when debugging [!INCLUDE[tsql](../../includes/tsql-md.md)].  
 
-## See Also  
- [Specify a Hit Count](../../relational-databases/scripting/specify-a-hit-count.md)   
- [Specify a Breakpoint Action](../../relational-databases/scripting/specify-a-breakpoint-action.md)   
- [Specify a Breakpoint Condition](../../relational-databases/scripting/specify-a-breakpoint-condition.md)   
- [Specify a Breakpoint Filter](../../relational-databases/scripting/specify-a-breakpoint-filter.md)  
+## See Also
+
+- [Specify a Hit Count](../../relational-databases/scripting/specify-a-hit-count.md)
+- [Specify a Breakpoint Action](../../relational-databases/scripting/specify-a-breakpoint-action.md)
+- [Specify a Breakpoint Condition](../../relational-databases/scripting/specify-a-breakpoint-condition.md)
+- [Specify a Breakpoint Filter](../../relational-databases/scripting/specify-a-breakpoint-filter.md)

docs/ssms/scripting/enable-disable-and-delete-breakpoints.md

@@ -1,20 +1,26 @@
 ---
-title: "Enable, Disable, and Delete Breakpoints"
-ms.custom: ""
-ms.date: "03/01/2017"
+title: Enable, Disable, and Delete Breakpoints
+titleSuffix: T-SQL debugger
 ms.prod: sql
 ms.prod_service: "sql-tools"
 ms.technology: scripting
-ms.reviewer: ""
 ms.topic: conceptual
 ms.assetid: 357b5874-273f-43a9-8e30-83872bdea5dc
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
+ms.custom: ""
+ms.date: 12/04/2019
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
+
 # Enable, Disable, and Delete Breakpoints
-[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
-  To view and manage all the open breakpoints, you can use the **Breakpoints** window. Use the window to view breakpoint information and to take actions such as deleting, disabling, or enabling breakpoints.  
+
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+
+To view and manage all the open breakpoints, you can use the **Breakpoints** window. Use the window to view breakpoint information and to take actions such as deleting, disabling, or enabling breakpoints.
+
+[!INCLUDE[ssms-old-versions](../../includes/ssms-old-versions.md)]
 
 ## The Breakpoints Window  
  The **Breakpoints** window lists information such as which line of code the breakpoint is located on. In the **Breakpoints** window, you can also delete, disable, and enable breakpoints. For more information about the **Breakpoints** window, see [Breakpoints Window](../../relational-databases/scripting/transact-sql-debugger-breakpoints-window.md)  

docs/ssms/scripting/specify-a-breakpoint-action.md

@@ -1,27 +1,34 @@
 ---
-title: "Specify a Breakpoint Action"
-ms.custom: ""
-ms.date: "03/14/2017"
+title: Specify a Breakpoint Action
+titleSuffix: T-SQL debugger
 ms.prod: sql
 ms.technology: scripting
-ms.reviewer: ""
 ms.topic: conceptual
 helpviewer_keywords: 
   - "Transact-SQL debugger, breakpoint action"
   - "Transact-SQL debugger, breakpoint when hit action"
 ms.assetid: f97f0097-6f51-40c1-b2e0-294a93ce1e1b
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
+ms.custom: ""
+ms.date: 12/04/2019
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
+
 # Specify a Breakpoint Action
-[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
-  A breakpoint **When Hit** action specifies a custom task that the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger performs for a breakpoint. If the specified hit count is reached and any specified breakpoint condition is satisfied, the debugger performs the action specified for the breakpoint.  
-  
-##  <a name="BKMK_ActionConsiderations"></a> Action Considerations  
- The default action for a breakpoint is to break execution when both the hit count and breakpoint condition have been satisfied. The primary use of a **When Hit** action in the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger is to instead print information to the debugger **Output** window by specifying a print message.  
-  
- A print message is specified in the **Print a Message** option, and is specified as a text string that includes expressions containing information from the [!INCLUDE[tsql](../../includes/tsql-md.md)] being debugged. Expressions include:  
+
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+
+A breakpoint **When Hit** action specifies a custom task that the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger performs for a breakpoint. If the specified hit count is reached and any specified breakpoint condition is satisfied, the debugger performs the action specified for the breakpoint.
+
+[!INCLUDE[ssms-old-versions](../../includes/ssms-old-versions.md)]
+  
+##  <a name="BKMK_ActionConsiderations"></a> Action Considerations
+
+The default action for a breakpoint is to break execution when both the hit count and breakpoint condition have been satisfied. The primary use of a **When Hit** action in the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger is to instead print information to the debugger **Output** window by specifying a print message.  
+  
+A print message is specified in the **Print a Message** option, and is specified as a text string that includes expressions containing information from the [!INCLUDE[tsql](../../includes/tsql-md.md)] being debugged. Expressions include:  
 
 -   A [!INCLUDE[tsql](../../includes/tsql-md.md)] expression contained in curly braces ({}). The expressions can include [!INCLUDE[tsql](../../includes/tsql-md.md)] variables, parameters, and built-in functions. Examples include {@MyVariable}, {@NameParameter}, {@@SPID}, or {SERVERPROPERTY('ProcessID')}.  
 

docs/ssms/scripting/specify-a-breakpoint-condition.md

@@ -1,42 +1,50 @@
 ---
-title: "Specify a Breakpoint Condition"
-ms.custom: ""
-ms.date: "03/14/2017"
+title: Specify a Breakpoint Condition
+titleSuffix: T-SQL debugger
 ms.prod: sql
 ms.technology: scripting
-ms.reviewer: ""
 ms.topic: conceptual
 helpviewer_keywords: 
   - "Transact-SQL debugger, breakpoint conditions"
 ms.assetid: b43d8a2b-99a3-4fb7-8848-99c042ea7ef7
 author: markingmyname
 ms.author: maghan
+ms.custom: ""
+ms.reviewer: ""
+ms.date: 12/04/2019
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
+
 # Specify a Breakpoint Condition
-[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
-  A breakpoint condition is a [!INCLUDE[tsql](../../includes/tsql-md.md)] expression that is evaluated by the debugger when the breakpoint is reached. If the condition is satisfied and any specified hit count reached, the debugger either breaks or performs the action specified for the breakpoint.  
-  
-## Specifying Conditions  
- The expression specified must be a valid Transact-SQL expression that evaluates to a Boolean value. For more information, see [Expressions (Transact-SQL)](../../t-sql/language-elements/expressions-transact-sql.md).  
+
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+
+A breakpoint condition is a [!INCLUDE[tsql](../../includes/tsql-md.md)] expression that is evaluated by the debugger when the breakpoint is reached. If the condition is satisfied and any specified hit count reached, the debugger either breaks or performs the action specified for the breakpoint.  
+
+[!INCLUDE[ssms-old-versions](../../includes/ssms-old-versions.md)]
+
+## Specifying Conditions
+
+The expression specified must be a valid Transact-SQL expression that evaluates to a Boolean value. For more information, see [Expressions (Transact-SQL)](../../t-sql/language-elements/expressions-transact-sql.md).  
 
  If you specify a breakpoint condition with invalid syntax, a warning message appears immediately. If you specify a condition with valid syntax but invalid semantics, a warning message is displayed the first time the breakpoint is hit. In either case, the debugger breaks execution when the invalid breakpoint is hit.  
 
-#### To Specify a Condition  
+#### To Specify a Condition
 
-1.  In the editor window, right-click the breakpoint glyph, and then click **Condition** on the shortcut menu.  
+1. In the editor window, right-click the breakpoint glyph, and then click **Condition** on the shortcut menu.  
 
      -or-  
 
      In the **Breakpoints** window, right-click the breakpoint glyph, and then click **Condition** on the shortcut menu.  
 
-2.  In the **Breakpoint Condition** dialog box, enter a valid Boolean expression in the **Condition** box.  
+2. In the **Breakpoint Condition** dialog box, enter a valid Boolean expression in the **Condition** box.  
 
-3.  Choose **Is true** if you want to break when the expression evaluates to **true**, or choose **Has changed** if you want to break when the value of the expression has changed.  
+3. Choose **Is true** if you want to break when the expression evaluates to **true**, or choose **Has changed** if you want to break when the value of the expression has changed.  
 
     > [!NOTE]  
     >  The debugger does not evaluate the Boolean expression until the first time the breakpoint is reached. If you choose **Has changed**, the debugger does not consider the first evaluation to be a change, so the debugger will not break on the first evaluation.  
   
-## See Also  
- [Specify a Hit Count](../../relational-databases/scripting/specify-a-hit-count.md)   
- [Specify a Breakpoint Action](../../relational-databases/scripting/specify-a-breakpoint-action.md)  
+## See Also
+
+- [Specify a Hit Count](../../relational-databases/scripting/specify-a-hit-count.md)
+- [Specify a Breakpoint Action](../../relational-databases/scripting/specify-a-breakpoint-action.md)

docs/ssms/scripting/specify-a-breakpoint-filter.md

@@ -1,24 +1,31 @@
 ---
 title: "Specify a Breakpoint Filter"
-ms.custom: ""
-ms.date: "03/14/2017"
+titleSuffix: T-SQL debugger
 ms.prod: sql
 ms.technology: scripting
-ms.reviewer: ""
 ms.topic: conceptual
 helpviewer_keywords: 
   - "Transact-SQL debugger, breakpoint filter"
 ms.assetid: 7bf1dddd-7b0b-4c47-8a7b-28a5569b4fa5
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
+ms.custom: ""
+ms.date: 12/04/2019
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
+
 # Specify a Breakpoint Filter
-[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
-  A breakpoint filter limits the breakpoint to acting only on specified computers, operating system processes, and threads. Breakpoint filters are typically used when debugging parallel applications.  
-  
-##  <a name="BKMK_ActionConsiderations"></a> Filter Considerations  
- Breakpoint filters are not typically used with the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger because [!INCLUDE[tsql](../../includes/tsql-md.md)] scripts and stored procedures are not parallel applications.  
+
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+
+A breakpoint filter limits the breakpoint to acting only on specified computers, operating system processes, and threads. Breakpoint filters are typically used when debugging parallel applications.
+
+[!INCLUDE[ssms-old-versions](../../includes/ssms-old-versions.md)]
+  
+##  <a name="BKMK_ActionConsiderations"></a> Filter Considerations
+
+Breakpoint filters are not typically used with the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger because [!INCLUDE[tsql](../../includes/tsql-md.md)] scripts and stored procedures are not parallel applications.  
 
 #### To Specify a Breakpoint Filter  
 

docs/ssms/scripting/specify-a-hit-count.md

@@ -1,10 +1,8 @@
 ---
-title: "Specify a Hit Count"
-ms.custom: ""
-ms.date: "03/14/2017"
+title: Specify a Hit Count
+titleSuffix: T-SQL debugger
 ms.prod: sql
 ms.technology: scripting
-ms.reviewer: ""
 ms.topic: conceptual
 f1_keywords: 
   - "vs.debug.breakpt.hitcount"
@@ -13,13 +11,22 @@ helpviewer_keywords:
 ms.assetid: 24836939-94ed-4e57-aa85-5d6938d859e4
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
+ms.custom: ""
+ms.date: 12/04/2019
 monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
 ---
+
 # Specify a Hit Count
-[!INCLUDE[appliesto-ss-asdb-asdw-pdw-md](../../includes/appliesto-ss-asdb-asdw-pdw-md.md)]
-  A breakpoint hit count is a counter that is incremented by the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger each time the breakpoint is reached. If the specified hit count is reached and any specified breakpoint condition is satisfied, the debugger performs the action specified for the breakpoint.  
-  
-## Hit Count Considerations  
+
+[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
+
+A breakpoint hit count is a counter that is incremented by the [!INCLUDE[tsql](../../includes/tsql-md.md)] debugger each time the breakpoint is reached. If the specified hit count is reached and any specified breakpoint condition is satisfied, the debugger performs the action specified for the breakpoint.  
+
+[!INCLUDE[ssms-old-versions](../../includes/ssms-old-versions.md)]
+
+## Hit Count Considerations
+
  By default, execution breaks every time a breakpoint is hit. You can choose between the following options:  
 
 -   Break always (the default).