Resolved

Select the drop down arrow and select "Save"?

Correct

Correct

Correct

We are using Source: PSOFT // ETL Data-Sync // Target: ADW // Design DVD. We are having issue in our FACT table design that pull from the PSOFT transaction tables. I am sure it was self-inflicted. We are in a high level frustration at the moment. Thanks

The concurrency is controlled from the Job - the default value for #Parallel Tasks is 10. You could reduce it to your comfort level.

Thank You. I can see my Prune time had no effect. Do I need to select / click "Generate" after I select my Prune time?

Connections / Source-Targets / Edit Check your URL and JDBC Driver

One more question. I set the Prune time yesterday and my process ran this morning. Is there a log file that will tell me wjat refresh date/time used? If all went well it should show 12:04 AM 04/30/2019 not 09:04 am 04/30/2019

Thanks for all your help!

Thank You So Much!!!! This is a great help. BTW is this information documented anywhere? 

We want to alter the SOURCE_REFRESH_TIMESTAMP and TARGET_REFRESH_TIMESTAMP from its set time (7:00 AM) to 12:01 AM) for each FACT table

We want to alter the SOURCE_REFRESH_TIMESTAMP and TARGET_REFRESH_TIMESTAMP from its set time (7:00 AM) to 12:01 AM) for each FACT table

We use data (PSOFT) that is always one day old. Our Prod data is moved into our FINT DB at 12:01AM every night. At the 7:00 AM that morning Data-Sync runs. Our counts are always off because of the refresh date and the "Entered/Update" dates in Data-Sync is off by 12 hours or more. We need a way to compensate for this…

Thanks for the help. Is it possible to access the refresh dates outside data-sync?

Maybe this is it. Looks like 909 inserted and 5000 updated LOG: C:\OAC\OACDataSync_V2_5\log\BHS_OAC_DS_PSOFT-VOUCHER_DATA.25940821 Truncate Stage TableSQL: TRUNCATE TABLE "S1#FACT_VOUCHER_PO"Stored Procedure: falseContinue on error: falseNumber of retries: 1 361 GLOBAL 2019-04-28 07:02:29.707 EST Reader1 - 5909 records…

FOUND WHAT i NEEDED Load Strategies A load strategy defines how your data is loaded from a specific data source into your target. When you choose a load strategy that incrementally loads the data, Data Sync requires you to define a user key to uniquely identify a record on the target side, and a DATE/TIMESTAMP based column…

Migrate Data Sync content from Non-Prod(Dev) to Prod Login to Non-Prod DS (Dev – NTBHI2012). Export DS metadata from DataSync à Tools à Export. Note: Make sure you select “Logical” and “System” when you are migrating for the first time. System option brings over connectivity and other universal settings. Subsequent…

I deleted and rewrote the SQL. It is now working