Merge branch 'main' into release-bdc-2022

Author: v-alje

docs/integration-services/connection-manager/integration-services-ssis-connections.md

@@ -108,7 +108,7 @@ A connection manager can be created at the package level or at the project level
   
 |Type|Description|Topic|  
 |----------|-----------------|-----------|  
-|ORACLE|Connects to an Oracle \<version info\> server.|The Oracle connection manager is the connection manager component of the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for Oracle by Attunity. The [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for Oracle by Attunity also includes a source and a destination. For more information, see the download page, [Microsoft Connectors for Oracle and Teradata by Attunity](https://www.microsoft.com/download/details.aspx?id=55179).|  
+|ORACLE|Connects to an Oracle \<version info\> server.|The Oracle connection manager is the connection manager component of the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for Oracle by Attunity. The [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for Oracle by Attunity also includes a source and a destination. For more information, see the download page, [Microsoft Connector for Oracle](https://www.microsoft.com/en-us/download/details.aspx?id=58228).|  
 |SAPBI|Connects to an SAP NetWeaver BI version 7 system.|The SAP BI connection manager is the connection manager component of the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for SAP BI. The [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for SAP BI also includes a source and a destination. For more information, see the download page, [Microsoft SQL Server 2008 Feature Pack](https://www.microsoft.com/download/details.aspx?id=44277).|  
 |TERADATA|Connects to a Teradata \<version info\> server.|The Teradata connection manager is the connection manager component of the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for Teradata by Attunity. The [!INCLUDE[msCoName](../../includes/msconame-md.md)] Connector for Teradata by Attunity also includes a source and a destination. For more information, see the download page, [Microsoft Connectors for Oracle and Teradata by Attunity](https://www.microsoft.com/download/details.aspx?id=55179).|  
 

docs/integration-services/devops/ssis-devops-overview.md

@@ -166,13 +166,12 @@ SSIS Deploy task currently doesn't support the following scenarios:
 - Configuring the environment in the SSIS catalog.
 - Deploying ISPAC to Azure SQL Server or Azure SQL Managed Instance, which allow only multifactor authentication.
 - Deploying packages to MSDB or SSIS Package Store.
-- Uploading to an on-premises DevOps server might result in the error "The extension package size exceeds the maximum package size". To resolve the error, first complete the following steps. If the error persists, please contact Azure DevOps support. 
-  1. Get the publisher name of the extension you want to increase the size limit for. The publisher name typically is on the left side of the `.` character in the URL of the extension's item details page in Azure Marketplace. For example, if the extension’s item details page is `https://marketplace.visualstudio.com/items?itemName=tylermurry.pr-auto-comment`, the publisher name is `tylermurry`.
+- If you install the SSIS DevOps Tools extension in Azure DevOps Server, you might see the message "The extension package size exceeds the maximum package size." To resolve the issue, complete the following steps: 
   1. Connect to the on-premises SQL Server instance and select the database **Gallery_Configuration**.
-  1. Run this query by replacing `<publisherName>` with the publisher name from step 1:  
-     `INSERT INTO dbo.tbl_RegistryItems VALUES (1,'#\Configuration\Service\Gallery\LargeExtensionUpload\<publisherName>\','MaxPackageSizeMB\',50)`  
-     Change `50` to a higher number if the extension is larger than 50 MBs.
+  1. Run the query `INSERT INTO dbo.tbl_RegistryItems VALUES (1,'#\Configuration\Service\Gallery\LargeExtensionUpload\SSIS\','MaxPackageSizeMB\',50)`. Change `50` to a higher number if the extension is larger than 50 MBs.
   1. After you run the query, restart Internet Information Services. Try again to upload the extension.
+  1. If the error persists, please contact Azure DevOps support. 
+
 
 ## SSIS Deploy task version 1.* 
 

docs/integration-services/lesson-5-1-copying-the-lesson-4-package.md

@@ -32,9 +32,9 @@ Use this procedure if you're copying the completed Lesson 4.  To copy the sample
 
 4.  In **Solution Explorer**, right-click **SSIS Packages** and then select **Paste**.
 
-    By default, the name of the copied package is **Lesson 4.dtsx**.
+    By default, the name of the copied package is **Lesson 5.dtsx**.
 
-5.  In **Solution Explorer**, double-click **Lesson 4.dtsx** to open the package.
+5.  In **Solution Explorer**, double-click **Lesson 5.dtsx** to open the package.
 
 6.  Right-click anywhere in the background of the **Control Flow** design surface and select **Properties**.
 

docs/integration-services/performance/integration-services-ssis-logging.md

@@ -378,11 +378,22 @@ ms.author: chugu
 9. To save the updated package, click **Save Selected Items** on the **File** menu.  
 
 ## <a name="server_logging"></a> Enable Logging for Package Execution on the SSIS Server
-  This topic describes how to set or change the logging level for a package when you run a package that you have deployed to the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] server. The logging level you set when you run the package overrides the package logging you configure at design time in [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)]. See [Enable Package Logging in SQL Server Data Tools](#ssdt) for more information.  
-  
- In SQL Server **Server Properties**, under the **Server logging level** property, you can select a default server-wide logging level. You can pick from one of the built-in logging levels described in this topic, or you can pick an existing customized logging level. The selected logging level applies by default to all packages deployed to the SSIS Catalog. It also applies by default to a SQL Agent job step that runs an SSIS package.  
-  
- You can also specify the logging level for an individual package by using one of the following methods. This topic covers the first method.  
+
+This topic describes how to set or change the logging level for a package when you run a package that you have deployed to the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] server. The logging level you set when you run the package overrides the package logging you configure at design time in [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)]. See [Enable Package Logging in SQL Server Data Tools](#ssdt) for more information.  
+
+### To review and adjust a server's default logging level property
+
+1. In the SQL Server instance, go to the package in Object Explorer.
+
+2. Select **Integration Services Catalog**.
+
+3. Right-click **SSISDB** and select **Properties**.
+
+4. In **Catalog Properties**, look for the **Operations Log** group box and the **Service-Wide Default Logging Level** entry.
+
+You can pick from one of the built-in logging levels described in this topic, or you can pick an existing customized logging level. The selected logging level applies by default to all packages deployed to the SSIS Catalog. It also applies by default to a SQL Agent job step that runs an SSIS package.  
+ 
+You can also specify the logging level for an individual package by using one of the following methods. This topic covers the first method.  
 
 -   Configuring an instance of a package execution by using the Execute Package dialog box  
 

docs/integration-services/system-views/catalog-executions-ssisdb-database.md

@@ -35,6 +35,8 @@ ms.author: chugu
 |executed_as_sid|**varbinary(85)**|The SID of the user who started the instance of execution.|  
 |executed_as_name|**nvarchar(128)**|The name of the database principal that was used to start the instance of execution.|  
 |use32bitruntime|**bit**|Indicates if the 32-bit runtime is used to run the package on a 64-bit operating system. When the value is `1`, the execution is performed with the 32-bit runtime. When the value is `0`, the execution is performed with the 64-bit runtime.|  
+|operation_type|**smallint**|The type of operation. The operation_type of 200 means create/start execution.|  
+|created_time|**datetimeoffset**|The time when the instance was initiated.  Keep in mind that there is a lag time between initiation and actual start time.| 
 |object_type|**smallint**|The type of object. The object may be a project (`20`) or a package (`30`).|  
 |object_id|**bigint**|The ID of the object affected by the operation.|  
 |status|**int**|The status of the operation. The possible values are created (`1`), running (`2`), canceled (`3`), failed (`4`), pending (`5`), ended unexpectedly (`6`), succeeded (`7`), stopping (`8`), and completed (`9`).|  
@@ -45,10 +47,10 @@ ms.author: chugu
 |process_id|**int**|The process ID of the external process, if applicable.|  
 |stopped_by_sid|**varbinary(85)**|The security ID (SID) of the user who stopped the instance of execution.|  
 |stopped_by_name|**nvarchar(128)**|The name of the user who stopped the instance of execution.|  
-|total_physical_memory_kb|**bigint**|The total physical memory (in megabytes) on the server when the execution is started.|  
-|available_physical_memory_kb|**bigint**|The available physical memory (in megabytes) on the server when the execution is started.|  
-|total_page_file_kb|**bigint**|The total page memory (in megabytes) on the server when the execution is started.|  
-|available_page_file_kb|**bigint**|The available page memory (in megabytes) on the server when the execution is started.|  
+|total_physical_memory_kb|**bigint**|The total physical memory (in kilobytes) on the server when the execution is started.|  
+|available_physical_memory_kb|**bigint**|The available physical memory (in kilobytes) on the server when the execution is started.|  
+|total_page_file_kb|**bigint**|The total page memory (in kilobytes) on the server when the execution is started.|  
+|available_page_file_kb|**bigint**|The available page memory (in kilobytes) on the server when the execution is started.|  
 |cpu_count|**int**|The number of logical CPUs on the server when the execution is started.|  
 |server_name|**nvarchar(128)**|The Windows server and instance information for a specified instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].|  
 |machine_name|**nvarchar(128)**|The computer name on which the server instance is running.|  

docs/integration-services/system-views/catalog-operations-ssisdb-database.md

@@ -51,6 +51,7 @@ ms.author: chugu
 |`2`|Retention window<br /><br /> (SQL Agent job)|**NULL**|**NULL**|  
 |`3`|MaxProjectVersion<br /><br /> (SQL Agent job)|**NULL**|**NULL**|  
 |`101`|**deploy_project**<br /><br /> (Stored procedure)|Project ID|Project name|  
+|`102`|**get_project**<br /><br /> (Stored procedure)|Project ID|Project name|  
 |`106`|**restore_project**<br /><br /> (Stored procedure)|Project ID|Project name|  
 |`200`|**create_execution** and **start_execution**<br /><br /> (Stored procedures)|Project ID|**NULL**|  
 |`202`|**stop_operation**<br /><br /> (Stored procedure)|Project ID|**NULL**|