Skip to main content
To homepage To homepage
Solved

Pre-script results in error

  • February 23, 2023
  • 4 replies
  • 61 views
R
Starter

v20.10.36.64

Hi,

I have set up a simple script action as follows to set the LAST_CHANGE_DATETIME column to the ENTRY_DATETIME value if it is NULL.

Script action

 

This works fine when selecting from the table in SSMS:

SSMS results using same script action

The script is set as a pre-script to the ADO.NET transfer on the execute step, but when I execute the table, the following error appears:

Incorrect syntax near 'LAST_CHANGE_DATETIME'.

Can I implement this simple script action as a pre-script? The idea is that I can then use a fully populated LAST_CHANGE_DATETIME column for incremental loads on my ledger table.

Thanks,

Richard

 

Best answer by rory.smith

This will not work because you cannot modify source data before loading it into TimeXtender. Why not make two incremental selection rules, one for each field?

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

    4 replies

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 649 replies
    • Answer
    • February 23, 2023

    This will not work because you cannot modify source data before loading it into TimeXtender. Why not make two incremental selection rules, one for each field?

    R
    1 person likes this
    • R
      richardray
    rvgfox
    Problem Solver
    Forum|alt.badge.img+4
    • rvgfox
    • Problem Solver
    • 222 replies
    • February 23, 2023

    @richardray I think that if you use that code in a pre-script, it must be a UPDATE, INSERT or DELETE sentence...

    R
    1 person likes this
    • R
      richardray
    R
    Starter
    • richardray
    • Author
    • Starter
    • 4 replies
    • February 23, 2023
    rory.smith wrote:

    This will not work because you cannot modify source data before loading it into TimeXtender. Why not make two incremental selection rules, one for each field?

    Thanks Rory. Will that work in the same way as having the two columns combined, i.e. what I was trying to achieve? I suppose if the primary key is configured correctly it will pick up any records where either date is greater than the previous execution.

    rory.smith
    TimeXtender Xpert
    Forum|alt.badge.img+7
    • rory.smith
    • TimeXtender Xpert
    • 649 replies
    • February 24, 2023

    It depends very much on how the columns are populated in your source system. This situation occurs in some source systems I have worked on, but I would simply test.

     

    If using two rules does not work with your source, another option is to load two sets: one based on incremental field and another on the other and resolve between those two inside your staging area

    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