Merge pull request #22272 from nilabjaball/f1

tamarakhader · web-flow · commit 0f522f83f2f9 · 2022-05-31T18:50:41.000-04:00
F1
diff --git a/docs/azure-data-studio/extensions/database-migration-assessment-for-oracle-extension.md b/docs/azure-data-studio/extensions/database-migration-assessment-for-oracle-extension.md
@@ -121,7 +121,7 @@ The SKU recommendation provides the suitable Azure SQL target, its service tier
 The SKU  recommendation evaluates various performance metrics - CPU, memory, IOPS, latency and storage. Based on the usage and the configuration data, the recommender provides the suitable SQL target and the appropriate service tier.
 
 > [!Note]
-> If automatic workload repository (AWR) feature is enabled at Oracle instance, then the SKU recommender will use the DBA_HIST_ views to gather the performance metrics metadata. Otherwise, the recommender will use server configuration and other system views information for sizing the Azure SQL target.
+> If automatic workload repository (AWR) feature is enabled at Oracle instance, then SKU recommender will use the DBA_HIST_ views to gather the performance metrics metadata. Otherwise, the recommender will use server configuration and other system views information for sizing the Azure SQL target.
 
 The feature assessment provides the Oracle to Azure SQL mapped features and the effort required for migrating those capabilities to Azure SQL target.
 
diff --git a/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-demo.png b/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-demo.png
diff --git a/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-run-new-oracle-assessment.png b/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-run-new-oracle-assessment.png
diff --git a/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-select-oracle-assessment.png b/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-select-oracle-assessment.png
diff --git a/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-view-assessment.png b/docs/azure-data-studio/extensions/media/database-migration-assessment-for-oracle-extension/dmafo-view-assessment.png
diff --git a/docs/ssma/db2/advanced-object-selection-db2tosql.md b/docs/ssma/db2/advanced-object-selection-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: ca098c15-c343-4d7d-a284-c2fc405eb991
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.multichecktreeview.f1"
+
 ---
 # Advanced Object Selection (DB2ToSQL)
 The **Advanced Object Section** dialog box lets you filter database objects by using strings and substrings in the object name, and then select or deselect those objects. SSMA performs conversion and migration operations on selected objects.  
diff --git a/docs/ssma/db2/assessing-db2-schemas-for-conversion-db2tosql.md b/docs/ssma/db2/assessing-db2-schemas-for-conversion-db2tosql.md
@@ -10,6 +10,8 @@ ms.topic: conceptual
 ms.assetid: 8892f5a4-72ba-4406-8649-7a9d67f4c1d9
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.assessment.f1"
 ---
 # Assessing DB2 Schemas for Conversion (DB2ToSQL)
 Before you load objects and migrate data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you should determine how complex the migration will be and how much time the migration will take. SSMA can create an assessment report that shows the percentage of objects that will be successfully converted. SSMA also lets you view the specific issues that cause conversion failures.  
diff --git a/docs/ssma/db2/assessment-report-db2tosql.md b/docs/ssma/db2/assessment-report-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: 9e13eba0-e3cf-4205-974f-c00f982061de
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.assessmentreport.f1"
+
 ---
 # Assessment Report (DB2ToSQL)
 The Assessment Report window shows the results of the conversion of database objects to [!INCLUDE[tsql](../../includes/tsql-md.md)] syntax, and can also help you estimate the complexity and cost of your migration projects.  
diff --git a/docs/ssma/db2/connect-to-db2-db2tosql.md b/docs/ssma/db2/connect-to-db2-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: 9d485fd0-ab5d-402a-a59a-e9982a61b7de
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.connectdb2mfform.f1"
+
 ---
 # Connect To DB2 (DB2ToSQL)
 Use the **Connect to DB2** dialog box to connect to the DB2 database that you want to migrate.  
diff --git a/docs/ssma/db2/connect-to-sql-server-db2tosql.md b/docs/ssma/db2/connect-to-sql-server-db2tosql.md
@@ -10,6 +10,8 @@ ms.topic: conceptual
 ms.assetid: bc14a072-8949-4ee0-a4b4-ada55fe8df5c
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.connectmssqlform.f1"
 ---
 # Connect to SQL Server (DB2ToSQL)
 Use the **Connect to SQL Server** dialog box to connect to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that you want to migrate to. To access the **Connect to SQL Server** dialog box, on the **File** menu, click **Connect to SQL Server**.  
diff --git a/docs/ssma/db2/converting-db2-schemas-db2tosql.md b/docs/ssma/db2/converting-db2-schemas-db2tosql.md
@@ -10,12 +10,14 @@ ms.topic: conceptual
 ms.assetid: 7947efc3-ca86-4ec5-87ce-7603059c75a0
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+  - "ssma.db2.convert.f1"
 ---
 # Converting DB2 Schemas (DB2ToSQL)
 After you have connected to DB2, connected to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], and set project and data mapping options, you can convert DB2 database objects to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database objects.  
   
 ## The Conversion Process  
-Converting database objects takes the object definitions from DB2, converts them to similar [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] objects, and then loads this information into the SSMA metadata. It does not load the information into the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. You can then view the objects and their properties by using the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Metadata Explorer.  
+Converting database objects takes the object definitions from DB2, converts them to similar [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] objects, and then loads this information into the SSMA metadata. It doesn't load the information into the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. You can then view the objects and their properties by using the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Metadata Explorer.  
   
 During the conversion, SSMA prints output messages to the Output pane and error messages to the Error List pane. Use the output and error information to determine whether you have to modify your DB2 databases or your conversion process to obtain the desired conversion results.  
   
@@ -27,20 +29,20 @@ The following table shows which DB2 objects are converted, and the resulting [!I
   
 |DB2 Objects|Resulting SQL Server Objects|  
 |-----------|----------------------------|  
-|Data Types|**SSMA maps every type except the following listed below:**<br /><br />CLOB: Some native functions for work with this type are not supported (e.g. CLOB_EMPTY())<br /><br />BLOB: Some native functions for work with this type are not supported  (e.g. BLOB_EMPTY())<br /><br />DBLOB: Some native functions for work with this type are not supported  (e.g. DBLOB_EMPTY())|  
-|User-Defined Types|**SSMA maps the following User-Defined:**<br /><br />Distinct Type<br /><br />Structured Type<br /><br />SQL PL data types - Note: Weak cursor type are not supported.|  
-|Special Registers|**SSMA only maps registers listed below:**<br /><br />CURRENT TIMESTAMP<br /><br />CURRENT DATE<br /><br />CURRENT TIME<br /><br />CURRENT TIMEZONE<br /><br />CURRENT USER<br /><br />SESSION_USER and USER<br /><br />SYSTEM_USER<br /><br />CURRENT CLIENT_APPLNAME<br /><br />CURRENT CLIENT_WRKSTNNAME<br /><br />CURRENT LOCK TIMEOUT<br /><br />CURRENT SCHEMA<br /><br />CURRENT SERVER<br /><br />CURRENT ISOLATION<br /><br />Other Special Registers are not mapped to SQL server semantic.|  
+|Data Types|**SSMA maps every type except the following listed below:**<br /><br />CLOB: Some native functions for work with this type is not supported (for example,  CLOB_EMPTY())<br /><br />BLOB: Some native functions for work with this type aren't supported  (for example,  BLOB_EMPTY())<br /><br />DBLOB: Some native functions for work with this type aren't supported  (for example,  DBLOB_EMPTY())|  
+|User-Defined Types|**SSMA maps the following User-Defined:**<br /><br />Distinct Type<br /><br />Structured Type<br /><br />SQL PL data types - Note: Weak cursor type aren't supported.|  
+|Special Registers|**SSMA only maps registers listed below:**<br /><br />CURRENT TIMESTAMP<br /><br />CURRENT DATE<br /><br />CURRENT TIME<br /><br />CURRENT TIMEZONE<br /><br />CURRENT USER<br /><br />SESSION_USER and USER<br /><br />SYSTEM_USER<br /><br />CURRENT CLIENT_APPLNAME<br /><br />CURRENT CLIENT_WRKSTNNAME<br /><br />CURRENT LOCK TIMEOUT<br /><br />CURRENT SCHEMA<br /><br />CURRENT SERVER<br /><br />CURRENT ISOLATION<br /><br />Other Special Registers aren't mapped to SQL server semantic.|  
 |CREATE TABLE|**SSMA maps CREATE TABLE with the following exceptions:**<br /><br />Multidimensional clustering (MDC) tables<br /><br />Range-clustered tables (RCT)<br /><br />Partitioned tables<br /><br />Detached table<br /><br />DATA CAPTURE clause<br /><br />IMPLICITLY HIDDEN option<br /><br />VOLATILE option|  
-|CREATE VIEW|SSMA maps CREATE VIEW with 'WITH LOCAL CHECK OPTION' but other options are not mapped to SQL server semantics|  
+|CREATE VIEW|SSMA maps CREATE VIEW with 'WITH LOCAL CHECK OPTION' but other options aren't mapped to SQL server semantics|  
 |CREATE INDEX|**SSMA maps CREATE INDEX with the following exceptions:**<br /><br />XML index<br /><br />BUSINESS_TIME WITHOUT OVERLAPS option<br /><br />PARTITIONED clause<br /><br />SPECIFICATION ONLY option<br /><br />EXTEND USING option<br /><br />MINPCTUSED option<br /><br />PAGE SPLIT option|  
 |Triggers|**SSMA maps the following trigger semantics:**<br /><br />AFTER / FOR EACH ROW Triggers<br /><br />AFTER /FOR EACH STATEMENT Triggers<br /><br />BEFORE / FOR EACH ROW and INSTEAD OF / FOR EACH ROW Triggers|  
 |Sequences|Are mapped.|  
-|SELECT Statement|**SSMA maps SELECT with the following exceptions:**<br /><br />Data-change-table-reference clause - Partially mapped, but FINAL tables does not supported<br /><br />Table-reference clause - Partially mapped, but only-table-reference, outer-table-reference, analyze_table-expression, collection-derived-table, xmltable-expression are not mapped to SQL server semantics<br /><br />Period-specification clause - Not mapped.<br /><br />Continue-handler clause - Not mapped.<br /><br />Typed-correlation clause - Not mapped.<br /><br />Concurrent-access-resolution clause - Not mapped.|  
+|SELECT Statement|**SSMA maps SELECT with the following exceptions:**<br /><br />Data-change-table-reference clause - Partially mapped, but FINAL tables don't supported<br /><br />Table-reference clause - Partially mapped, but only-table-reference, outer-table-reference, analyze_table-expression, collection-derived-table, xmltable-expression aren't mapped to SQL server semantics<br /><br />Period-specification clause - Not mapped.<br /><br />Continue-handler clause - Not mapped.<br /><br />Typed-correlation clause - Not mapped.<br /><br />Concurrent-access-resolution clause - Not mapped.|  
 |VALUES Statement|Is mapped.|  
 |INSERT Statement|Is mapped.|  
 |UPDATE Statement|S**SMA maps UPDATE with the following exceptions:**<br /><br />Table-reference clause - Only-table-reference is not mapped to SQL server semantics<br /><br />Period clause - Is not mapped.|  
-|MERGE Statement|**SSMA maps MERGE with the following exceptions:**<br /><br />Single vs Multiple Occurrences of Each Clause - Is mapped to SQL server semantics for limited occurrences of each clause<br /><br />SIGNAL Clause - Does not map to SQL Server semantics<br /><br />Mixed UPDATE and DELETE Clauses - Does not map to SQL Server semantics<br /><br />Period-clause - Does not map to SQL Server semantics|  
-|DELETE Statement|**SSMA maps DELETE with the following exceptions:**<br /><br />Table-reference clause - Only-table-reference is not mapped to SQL server semantics<br /><br />Period clause - Does not map to SQL Server semantics|  
+|MERGE Statement|**SSMA maps MERGE with the following exceptions:**<br /><br />Single vs Multiple Occurrences of Each Clause - Is mapped to SQL server semantics for limited occurrences of each clause<br /><br />SIGNAL Clause - doesn't map to SQL Server semantics<br /><br />Mixed UPDATE and DELETE Clauses - doesn't map to SQL Server semantics<br /><br />Period-clause - doesn't map to SQL Server semantics|  
+|DELETE Statement|**SSMA maps DELETE with the following exceptions:**<br /><br />Table-reference clause - Only-table-reference is not mapped to SQL server semantics<br /><br />Period clause - doesn't map to SQL Server semantics|  
 |Isolation Level and Lock Type|Is mapped.|  
 |Procedures (SQL)|Are mapped.|  
 |Procedures (external)|Require manual update.|  
@@ -55,14 +57,14 @@ The following table shows which DB2 objects are converted, and the resulting [!I
 |LEAVE Statement|Is mapped.|  
 |LOOP Statement|Is mapped.|  
 |REPEAT Statement|Is mapped.|  
-|RESIGNAL Statement|Conditions are not supported. Messages can be optional.|  
+|RESIGNAL Statement|Conditions aren't supported. Messages can be optional.|  
 |RETURN Statement|Is mapped.|  
-|SIGNAL Statement|Conditions are not supported. Messages can be optional.|  
+|SIGNAL Statement|Conditions aren't supported. Messages can be optional.|  
 |WHILE Statement|Is mapped.|  
-|GET DIAGNOSTICS Statement|**SSMA maps GET DIAGNOSTICS with the following exceptions:**<br /><br />ROW_COUNT - Is mapped.<br /><br />DB2_RETURN_STATUS - Is mapped.<br /><br />MESSAGE_TEXT - Is mapped.<br /><br />DB2_SQL_NESTING_LEVEL - Does not map to SQL Server semantics<br /><br />DB2_TOKEN_STRING - Does not map to SQL Server semantics|  
-|Cursors|**SSMA maps CURSORS with the following exceptions:**<br /><br />ALLOCATE CURSOR statement - Does not map to SQL Server semantics<br /><br />ASSOCIATE LOCATORS statement - Does not map to SQL Server semantics<br /><br />DECLARE CURSOR statement - Returnability clause is not mapped to SQL server semantics<br /><br />FETCH statement - Partial mapping. Variables as target are supported only. SQLDA DESCRIPTOR is not  mapped to SQL server semantics|  
+|GET DIAGNOSTICS Statement|**SSMA maps GET DIAGNOSTICS with the following exceptions:**<br /><br />ROW_COUNT - Is mapped.<br /><br />DB2_RETURN_STATUS - Is mapped.<br /><br />MESSAGE_TEXT - Is mapped.<br /><br />DB2_SQL_NESTING_LEVEL - doesn't map to SQL Server semantics<br /><br />DB2_TOKEN_STRING - doesn't map to SQL Server semantics|  
+|Cursors|**SSMA maps CURSORS with the following exceptions:**<br /><br />ALLOCATE CURSOR statement - doesn't map to SQL Server semantics<br /><br />ASSOCIATE LOCATORS statement - doesn't map to SQL Server semantics<br /><br />DECLARE CURSOR statement - Returnability clause is not mapped to SQL server semantics<br /><br />FETCH statement - Partial mapping. Variables as target are supported only. SQLDA DESCRIPTOR is not  mapped to SQL server semantics|  
 |Variables|Are mapped.|  
-|Exceptions, Handlers, and Conditions|**SSMA maps "exception handling" with the following exceptions:**<br /><br />EXIT Handlers - Are mapped.<br /><br />UNDO Handlers - Are mapped.<br /><br />CONTINUE Handlers - Are not mapped.<br /><br />Conditions - It does not map to SQL server semantics.|  
+|Exceptions, Handlers, and Conditions|**SSMA maps "exception handling" with the following exceptions:**<br /><br />EXIT Handlers - Are mapped.<br /><br />UNDO Handlers - Are mapped.<br /><br />CONTINUE Handlers - Aren't mapped.<br /><br />Conditions - It doesn't map to SQL server semantics.|  
 |Dynamic SQL|Not mapped.|  
 |Aliases|Are mapped.|  
 |Nicknames|Partial mapping. Manual processing is required for underlying object|  
@@ -132,7 +134,7 @@ For objects that failed conversion, you can view the syntax that resulted in the
   
     SSMA will highlight the first problematic source code it finds in the current object.  
   
-For each item that could not be converted, you have to determine what you want to do with that object:  
+For each item that could not be converted, you've to determine what you want to do with that object:  
   
 -   You can modify the source code for procedures on the **SQL** tab.  
   
diff --git a/docs/ssma/db2/data-migration-report-db2tosql.md b/docs/ssma/db2/data-migration-report-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: 46ebada7-db36-4ae9-b7ae-baa4b854b237
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.datamigrationreport.f1"
+
 ---
 # Data Migration Report (DB2ToSQL)
 The **Data Migration Report** dialog box appears after you migrate data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
diff --git a/docs/ssma/db2/global-settings-editor-db2tosql.md b/docs/ssma/db2/global-settings-editor-db2tosql.md
@@ -10,6 +10,8 @@ ms.topic: conceptual
 ms.assetid: a5029bcb-7d5d-44a0-ae28-0efd10d2a714
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.globalsettingeditor.f1"
 ---
 # Global Settings (Editor) (DB2ToSQL)
 Use the Editor page of the **Global Settings** dialog box to specify settings for code editor windows.  
diff --git a/docs/ssma/db2/global-settings-logging-db2tosql.md b/docs/ssma/db2/global-settings-logging-db2tosql.md
@@ -10,6 +10,8 @@ ms.topic: conceptual
 ms.assetid: d314a2ca-ea2e-46e0-ae5e-8774841da91b
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.globalsettinglogging.f1"
 ---
 # Global Settings (Logging) (DB2ToSQL)
 Use the **Global Settings** dialog box to specify the logging settings for SSMA. Typically, you would change these settings only when working with product support.  
diff --git a/docs/ssma/db2/global-settings-output-window-db2tosql.md b/docs/ssma/db2/global-settings-output-window-db2tosql.md
@@ -10,6 +10,8 @@ ms.topic: conceptual
 ms.assetid: f21f80f4-9a2a-448d-9fe8-b6926595389e
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.globalsettingoutputwindow.f1"
 ---
 # Global Settings (Output Window) (DB2ToSQL)
 Use the **Global Settings** dialog box to specify settings for SSMA.  
diff --git a/docs/ssma/db2/mapping-db2-and-sql-server-data-types-db2tosql.md b/docs/ssma/db2/mapping-db2-and-sql-server-data-types-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: e7e939a8-5e76-4509-beaf-5acd1cab505e
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.typemappingeditform.f1"
+
 ---
 # Mapping DB2 and SQL Server Data Types (DB2ToSQL)
 DB2 database types differ from [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database types. When you convert DB2 database objects to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] objects, you must specify how to map data types from DB2 to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. You can accept the default data type mappings, or you can customize the mappings as shown in the following sections.  
diff --git a/docs/ssma/db2/mapping-db2-schemas-to-sql-server-schemas-db2tosql.md b/docs/ssma/db2/mapping-db2-schemas-to-sql-server-schemas-db2tosql.md
@@ -10,6 +10,10 @@ ms.topic: conceptual
 ms.assetid: 05ff7bd4-e60b-4f48-a893-bc2346aa9a8a
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+  - "ssma.db2.schemamappingpanel.f1"
+ 
+
 ---
 # Mapping DB2 Schemas to SQL Server Schemas (DB2ToSQL)
 In DB2, each database has one or more schemas. By default, SSMA migrates all objects in an DB2 schema to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database named for the schema. However, you can customize the mapping between DB2 schemas and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] databases.  
diff --git a/docs/ssma/db2/migrating-db2-data-into-sql-server-db2tosql.md b/docs/ssma/db2/migrating-db2-data-into-sql-server-db2tosql.md
@@ -11,6 +11,8 @@ ms.topic: conceptual
 ms.assetid: 86cbd39f-6dac-409a-9ce1-7dd54403f84b
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+  - "ssma.db2.general.f1"
 ---
 # Migrating DB2 Data into SQL Server (DB2ToSQL)
 After you have successfully synchronized the converted objects with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you can migrate data from DB2 to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
diff --git a/docs/ssma/db2/migrating-db2-databases-to-sql-server-db2tosql.md b/docs/ssma/db2/migrating-db2-databases-to-sql-server-db2tosql.md
@@ -11,6 +11,9 @@ ms.topic: conceptual
 ms.assetid: 14d2e655-af7e-4aa5-ba28-0e3d0d025518
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.migratedata.f1"
+
 ---
 # Migrating DB2 Databases to SQL Server (DB2ToSQL)
 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Migration Assistant (SSMA) for DB2 is a comprehensive environment that helps you quickly migrate DB2 databases to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or Azure SQL Database. By using SSMA for DB2, you can review database objects and data, assess databases for migration, migrate database objects to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or Azure SQL Database, and then migrate data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] or Azure SQL Database. Note that you cannot migrate SYS and SYSTEM DB2 schemas.  
diff --git a/docs/ssma/db2/new-project-db2tosql.md b/docs/ssma/db2/new-project-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: 66437b45-4686-4fc7-a91b-ebde45e0f1b0
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.workspacedialog.f1"
+
 ---
 # New Project (DB2ToSQL)
 Use the **New Project** dialog box to create a new SSMA project. To access the **New Project** dialog box, on the **File** menu, click **New Project**.  
diff --git a/docs/ssma/db2/project-settings-conversion-db2tosql.md b/docs/ssma/db2/project-settings-conversion-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: 538c93cf-c5bb-43d5-b758-186d9fb00c19
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.projectsettingconvertion.f1"
+
 ---
 # Project Settings (Conversion) (DB2ToSQL)
 The Conversion page of the **Project Settings** dialog box contains settings that customize how SSMA converts DB2 syntax to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] syntax.  
diff --git a/docs/ssma/db2/project-settings-gui-db2tosql.md b/docs/ssma/db2/project-settings-gui-db2tosql.md
@@ -10,6 +10,9 @@ ms.topic: conceptual
 ms.assetid: b2cdb71a-f301-45b3-878c-382356c93b4b
 author: cpichuka 
 ms.author: cpichuka 
+f1_keywords: 
+    - "ssma.db2.projectsettingsgui.f1"
+
 ---
 # Project Settings (GUI) (DB2ToSQL)
 The GUI project settings let you configure how data appears on the **Data** tab and whether to show the assessment report after conversion or not.  
diff --git a/docs/ssma/db2/project-settings-loading-system-objects-db2tosql.md b/docs/ssma/db2/project-settings-loading-system-objects-db2tosql.md
diff --git a/docs/ssma/db2/project-settings-migration-db2tosql.md b/docs/ssma/db2/project-settings-migration-db2tosql.md
diff --git a/docs/ssma/db2/project-settings-type-mapping-db2tosql.md b/docs/ssma/db2/project-settings-type-mapping-db2tosql.md
