Merge pull request #20640 from MicrosoftDocs/master

11/09 PM Publish

Author: huypub

docs/relational-databases/track-changes/change-data-capture-and-other-sql-server-features.md

@@ -61,6 +61,8 @@ This topic describes how the following features interact with change data captur
      `SQL Server cannot load database '%.*ls' because change data capture is enabled. The currently installed edition of SQL Server does not support change data capture. Either restore database without KEEP_CDC option, or upgrade the instance to one that supports change data capture.`  
 
  You can use [sys.sp_cdc_disable_db](../../relational-databases/system-stored-procedures/sys-sp-cdc-disable-db-transact-sql.md) to remove change data capture from a restored or attached database.  
+ 
+ After restoring a database on Azure SQL Managed Instance, CDC will remain enabled, but you must ensure that the scan and cleanup jobs are added and running. You can manually add the jobs by running [sys.sp_cdc_add_job](https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sys-sp-cdc-add-job-transact-sql?view=sql-server-ver15). 
 
 ##  <a name="Contained"></a> Contained databases  
  Change data capture is not supported in [contained databases](../../relational-databases/databases/contained-databases.md).

docs/t-sql/database-console-commands/dbcc-tracestatus-transact-sql.md

@@ -50,7 +50,7 @@ Is the number of the trace flag for which the status is displayed. If *trace#*,
 Is a placeholder that indicates multiple trace flags can be specified.
 
 -1  
-Displays the status of trace flags that are enabled globally. If -1 is specified without *trace#*, all the global trace flags that are enabled are displayed.
+Displays the status of trace flags that are enabled globally and for the current session.  If -1 is specified without *trace#*, all trace flags including session enabled are returned.
 
 WITH NO_INFOMSGS  
 Suppresses all informational messages that have severity levels from 0 through 10.
@@ -65,7 +65,7 @@ The following table describes the information in the result set.
 |**Global**|Indicates whether the trace flag is set globally<br /><br /> 1 = True<br /><br /> 0 = False|  
 |**Session**|Indicates whether the trace flag is set for the session<br /><br /> 1 = True<br /><br /> 0 = False|  
 
-DBCC TRACESTATUS returns a column for the trace flag number and a column for the status. This indicates whether the trace flag is ON (1) or OFF (0). The column heading for the trace flag number is either **Global Trace Flag** or **Session Trace Flag**, depending on whether you are checking the status for a global or a session trace flag.
+DBCC TRACESTATUS returns a column for the trace flag number and a column for the status. This indicates whether the trace flag is ON (1) or OFF (0). The column heading for the trace flag number is either **Global** or **Session**, depending on whether you are checking the status for a global or a session trace flag.
 
 ## Remarks  
 In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], there are two types of trace flags: session and global. Session trace flags are active for a connection and are visible only for that connection. Global trace flags are set at the server level and are visible to every connection on the server.
@@ -88,7 +88,7 @@ DBCC TRACESTATUS (2528, 3205);
 GO  
 ```  
 
-The following example displays whether trace flag `3205` is enabled globally.
+The following example displays whether trace flag `3205` is enabled for the current session or globally.
 
 ```sql  
 DBCC TRACESTATUS (3205, -1);