Skip to main content
To homepage To homepage
Solved

Tables based on incremental table not deployable to snowflake

Roy V
Problem Solver
Forum|alt.badge.img+2
  • Roy V
  • Problem Solver
  • 56 replies

Good morning,

We upgraded to 6675 version and are now testing a deployment to snowflake.

The tables based on full load mappings deploy well (with our without simple mode)

When deploying tables who are based on an incremental ODX tabel we recieve an error on the syntax of the usp clean procedure TimeXtender wants to create in Snowflake.
The script TimeXtender creates starts with:

CREATE PROCEDURE "HIST_ETL"."usp_ReaturnTM_DimRentableUnitCommercial_Clean"
    :DWBATCHNR INT
WITH RECOMPILE

Snowflake doesn’t expect the : and returns:
Syntax error: unexpected ':'. (line 2)

Is this a known issue and if not, I hope it can be added to the wishlist with TimeXtender features that need to be made available against Snowflake storage. 
 

Best answer by Thomas Lind

Hi @Roy V 

I got this.

Just confirmed it's a bug that affects incremental load on simple mode.

So a workaround until the fix has been released, would be if you turned off simple mode on the incrementally loaded tables.

View original
    Did this topic help you find an answer to your question?

    3 replies

    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • 1035 replies
    • July 3, 2024

    Hi @Roy V 

    I asked if this is not supposed to work or if it is a bug.

    Roy V
    1 person likes this
    • Roy V
      Roy V
    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • 1035 replies
    • Answer
    • July 4, 2024

    Hi @Roy V 

    I got this.

    Just confirmed it's a bug that affects incremental load on simple mode.

    So a workaround until the fix has been released, would be if you turned off simple mode on the incrementally loaded tables.

    Roy V
    Problem Solver
    Forum|alt.badge.img+2
    • Roy V
    • Author
    • Problem Solver
    • 56 replies
    • July 4, 2024

    Thanks for the update Thomas and the workaround. We will use this combination again when the fix is released. 

    Reply


    Most helpful members this week

    Terms and ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings