+1
I want my transfer to MDW job to run only when my ODX transfer task has completed without any errors. What happens sometimes now is that for some reason there is an error in the extraction and some tables are empty, they then get pushed to the MDW and our reports break because the tables are empty. I see that you can use instance variables but I don’t see that option on my ODX. How can I set this up?
Best answer by Niels Jonker
View original
+5
Hi
+1
+5
+1
If you add it as an idea, I’ll upvote it :-)
(I’m happy to add it if you want)
+5
Hi
The reason I ask about error messages is because I would like to investigate if there is a particular error that results in empty tables, as I have not seen this happening on ODX Data Lake storage before. I just tested with a SQL server data source, and I removed a column in my source that I explicitly included in the table/column selection for the ODX data source, which resulted in an error when I transfer. No new parquet file was created in my ADLS, and therefore when I executed the table in my MDW the same data was present as before (i.e. records were not deleted). So in this test case, despite errors in transfer task, it did not lead to empty tables, which means there is no need to create a “rule” to only transfer data from the ODX when the transfer task was completed successfully without any errors.
In regards to “What happens sometimes now is that for some reason there is an error in the extraction and some tables are empty” - which data source are you using and can you please send the error messages for those failed extractions?
+1
+5
+1
+1
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
