Out-of-Scope

Examples of Out-of-scope code units if multiple SQL Languages

Description

As described in the conversion scope page, some code units are considered out of scope for conversion reasons. Here are some examples of how these code units are printed in the output folder.

Teradata

Function with unsupported language:

IN -> Teradata_01.sql

CREATE FUNCTION CFEXTERNALINC (p1 INTEGER)
  RETURNS TABLE(
     c1 INTEGER
   )
   LANGUAGE java
   NO SQL
   PARAMETER STYLE SQL
     EXTERNAL NAME 'CS!fnc_tbf001udt.c'

Snowflake output:

OUT -> Teradata_01.sql

----** SSC-OOS - OUT OF SCOPE CODE UNIT. CREATE FUNCTION IS OUT OF TRANSLATION SCOPE. **
--CREATE FUNCTION CFEXTERNALINC (p1 INTEGER)
--  RETURNS TABLE(
--     c1 INTEGER
--   )
--   LANGUAGE java
--   NO SQL
--   PARAMETER STYLE SQL
--     EXTERNAL NAME 'CS!fnc_tbf001udt.c'
                                       ;

Oracle

Wrapped type definition:

IN -> Oracle_01.sql

CREATE TYPE data_typ1 wrapped
a000000
b2
6CodpsEHq3I=

Snowflake output:

OUT -> Oracle_01.sql

----** SSC-OOS - OUT OF SCOPE CODE UNIT. Wrapped TYPE IS OUT OF TRANSLATION SCOPE. **
--CREATE TYPE data_typ1 wrapped
--a000000
--b2
--6CodpsEHq3I=

Transact SQL

Trigger:

IN -> Transact_01.sql

CREATE TRIGGER reminder1
ON Sales.Customer
AFTER INSERT, UPDATE
AS RAISERROR ('Notify Customer Relations', 16, 10);

Snowflake output:

OUT -> Transact_01.sql

----** SSC-OOS - OUT OF SCOPE CODE UNIT. CREATE TRIGGER IS OUT OF TRANSLATION SCOPE. **
--CREATE TRIGGER reminder1
--ON Sales.Customer
--AFTER INSERT, UPDATE
--AS RAISERROR ('Notify Customer Relations', 16, 10);

Recommendations

• If you need more support, you can email us at [email protected]