You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ssma/db2/converting-db2-schemas-db2tosql.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ f1_keywords:
17
17
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.
18
18
19
19
## The Conversion Process
20
-
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.
20
+
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.
21
21
22
22
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.
23
23
@@ -29,20 +29,20 @@ The following table shows which DB2 objects are converted, and the resulting [!I
29
29
30
30
|DB2 Objects|Resulting SQL Server Objects|
31
31
|-----------|----------------------------|
32
-
|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())|
33
-
|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.|
34
-
|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.|
32
+
|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())|
33
+
|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.|
|CREATE VIEW|SSMA maps CREATE VIEW with 'WITH LOCAL CHECK OPTION' but other options are not mapped to SQL server semantics|
36
+
|CREATE VIEW|SSMA maps CREATE VIEW with 'WITH LOCAL CHECK OPTION' but other options aren't mapped to SQL server semantics|
37
37
|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|
38
38
|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|
39
39
|Sequences|Are mapped.|
40
-
|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.|
40
+
|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.|
41
41
|VALUES Statement|Is mapped.|
42
42
|INSERT Statement|Is mapped.|
43
43
|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.|
44
-
|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|
45
-
|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|
44
+
|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|
45
+
|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|
46
46
|Isolation Level and Lock Type|Is mapped.|
47
47
|Procedures (SQL)|Are mapped.|
48
48
|Procedures (external)|Require manual update.|
@@ -57,14 +57,14 @@ The following table shows which DB2 objects are converted, and the resulting [!I
57
57
|LEAVE Statement|Is mapped.|
58
58
|LOOP Statement|Is mapped.|
59
59
|REPEAT Statement|Is mapped.|
60
-
|RESIGNAL Statement|Conditions are not supported. Messages can be optional.|
60
+
|RESIGNAL Statement|Conditions aren't supported. Messages can be optional.|
61
61
|RETURN Statement|Is mapped.|
62
-
|SIGNAL Statement|Conditions are not supported. Messages can be optional.|
62
+
|SIGNAL Statement|Conditions aren't supported. Messages can be optional.|
63
63
|WHILE Statement|Is mapped.|
64
-
|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|
65
-
|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|
64
+
|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|
65
+
|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|
66
66
|Variables|Are mapped.|
67
-
|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.|
67
+
|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.|
68
68
|Dynamic SQL|Not mapped.|
69
69
|Aliases|Are mapped.|
70
70
|Nicknames|Partial mapping. Manual processing is required for underlying object|
@@ -134,7 +134,7 @@ For objects that failed conversion, you can view the syntax that resulted in the
134
134
135
135
SSMA will highlight the first problematic source code it finds in the current object.
136
136
137
-
For each item that could not be converted, you have to determine what you want to do with that object:
137
+
For each item that could not be converted, you've to determine what you want to do with that object:
138
138
139
139
- You can modify the source code for procedures on the **SQL** tab.
0 commit comments