My Oracle Support Banner

SQL Developer SQL Server Migration Creates Trigger/sequence Instead Of Identity For Temp Tables (Doc ID 2684836.1)

Last updated on JULY 21, 2020

Applies to:

Oracle SQL Developer - Version 19.2 and later
Information in this document applies to any platform.

Symptoms

SQL Developer SQL Server Migration creates trigger/sequence instead of identity for Temp Tables.

Having normal tables in a SQLServer with identity columns and having Oracle
12c code generation checked SQL Developer correctly creates in Oracle
identity columns. But having a temp table in Oracle which is for example
created during a procedure call the SQL Server code is translated into the
old syntax using trigger & sequence

e.g




Same happens also with function that have a temp table definition inside:

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.