Skip to content

Commit f38843b

Browse files
authored
Update 1-design-performance-migration.md
Modify the data type mapping of the number type between ORACLE and Azure Synapse https://learn.microsoft.com/en-us/sql/relational-databases/polybase/polybase-type-mapping?view=sql-server-ver16#oracle-type-mapping-reference
1 parent 5483bb6 commit f38843b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/synapse-analytics/migration-guides/oracle/1-design-performance-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -300,7 +300,7 @@ Most Oracle data types have a direct equivalent in Azure Synapse. The following
300300
| LONG RAW | Not supported. Map to VARBINARY(MAX). |
301301
| NCHAR | NCHAR |
302302
| NVARCHAR2 | NVARCHAR |
303-
| NUMBER | NUMBER |
303+
| NUMBER | FLOAT |
304304
| NCLOB | Not directly supported. Replace with NVARCHAR(MAX). |
305305
| NUMERIC | NUMERIC |
306306
| ORD media data types | Not supported |
@@ -480,4 +480,4 @@ The [workload management guide](../../sql-data-warehouse/analyze-your-workload.m
480480
481481
## Next steps
482482
483-
To learn about ETL and load for Oracle migration, see the next article in this series: [Data migration, ETL, and load for Oracle migrations](2-etl-load-migration-considerations.md).
483+
To learn about ETL and load for Oracle migration, see the next article in this series: [Data migration, ETL, and load for Oracle migrations](2-etl-load-migration-considerations.md).

0 commit comments

Comments
 (0)