Azure Data Factory V2 – Incremental loading with configuration stored in a table – Complete solution, step by step.

This post explains things that are difficult to find even in English. That’s why I will break my rule and will not write it in my native language! Po wersję polską zapraszam do google translate :>

Introduction


Loading data using Azure Data Factory v2 is really simple. Just drop Copy activity to your pipeline, choose a source and sink table, configure some properties and that’s it – done with just a few clicks!

But what if you have dozens or hundreds of tables to copy? Are you gonna do it for every object?

Fortunately, you do not have to do this! All you need is dynamic parameters and a few simple tricks 🙂

Also, this will give you the option of creating incremental feeds, so that – at next run – it will transfer only newly added data.

Mappings

Before we start diving into details, let’s demystify some basic ADFv2 mapping principles.

  • Copy activity doesn’t need to have defined column mappings at all,
  • it can dynamically map them using its own mechanism which retrieves source and destination (sink) metadata,
  • if you use polybase, it will do it using column order (1st column from source to 1st column at destination etc.),
  • if you do not use polybase, it will map them using their names but watch out – it’s case sensitive matching!
  • So all you have to do is to just keep the same structure and data types on the destination tables (sink), as they are in a source database.

Bear in mind, that if your columns are different between source and destination, you will have to provide custom mappings. This tutorial doesn’t show how to do it, but it is possible to pass them using “Get metadata” activity to retrieve column specification from the source, then you have to parse it and pass as JSON structure into the mapping dynamic input. you can read about mappings in official documentation: https://docs.microsoft.com/en-us/azure/data-factory/copy-activity-schema-and-type-mapping

String interpolation – the key to success

My entire solution is based on one cool feature, that is called string interpolation. It is a part of built-in expression engine, that simply allows you to just inject any value from JSON object or an expression directly into string input, without any concatenate functions or operators. It’s fast and easy. Just wrap your expression between  @{ ... } . It will always return it as a string.

Below is a screen from official documentation, that clarifies how this feature works:

Read more about JSON expressions at https://docs.microsoft.com/en-us/azure/data-factory/control-flow-expression-language-functions#expressions

 

So what we are going to do? :>


Good question 😉

In my example, I will show you how to transfer data incrementally from Oracle and PostgreSQL tables into Azure SQL Database.

All of this using configuration stored in a table, which in short, keeps information about Copy activity settings needed to achieve our goal 🙂

Adding new definitions into config will also automatically enable transfer for them, without any need to modify Azure Data Factory pipelines.

So you can transfer as many tables as you want, in one pipeline, at once. Triggering with one click 🙂

 

Every process needs diagram :>

 

 

Basically, we will do:

  1. Get configuration from our config table inside Azure SQL Database using Lookup activity, then pass it to Filter activity to split configs for Oracle and PostgreSQL.
  2. In Foreach activity created for every type of database, we will create simple logic that retrieves maximum update date from every table.
  3.  Then we will prepare dynamically expressions for SOURCE and SINK properties in Copy activity. MAX UPDATEDATE, retrieved above, and previous WATERMARK DATE, retrieved from config, will set our boundaries in WHERE clause. Every detail like table name or table columns we will pass as a query using string interpolation, directly from JSON expression. Sink destination will be also parametrized.
  4. Now Azure Data Factory can execute queries evaluated dynamically from JSON expressions, it will run them in parallel just to speed up data transfer.
  5. Every successfully transferred portion of incremental data for a given table has to be marked as done. We can do this saving MAX UPDATEDATE in configuration, so that next incremental load will know what to take and what to skip. We will use here: Stored procedure activity.
This example simplifies the process as much as it is possible. Remember, in your solution you have to implement logic for every unsuccessful operation. You can achieve that using On Failure control flow with some activities (chosen depending on your needs) and timeout/retry options set individually for every activity in your pipeline.

 

About sources

I will use PostgreSQL 10 and Oracle 11 XE installed on my Ubuntu 18.04 inside VirtualBox machine.

In Oracle, tables and data were generated from EXMP/DEPT samples delivered with XE version.

In PostgreSQL – from dvd rental sample database: http://www.postgresqltutorial.com/postgresql-sample-database/

 

I simply chose three largest tables from each database. You can find them in a configuration shown below this section.

 

Every database is accessible from my Self-hosted Integration Runtime. I will show an example how to add the server to Linked Services, but skip configuring Integration Runtime. You can read about creating self-hosted IR here: https://docs.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime.

 

About configuration

In my Azure SQL Database I have created a simple configuration table:

Id is just an identity value, SRC_name is a type of source server (ORA or PG).

SRC and DST tab columns maps source and destination objects. Cols defines selected columns, Watermark Column and Value stores incremental metadata.

And finally Enabled just enables particular configuration (table data import).

As Andy rightly noted in the comment below this post, it is possible to use “Cols” also to implement SQL logic, like functions, aliases etc. The value from this column is rewritten directly to the query (more precisely – concatenated between SELECT and FROM clause). So you can use it according to your needs.

 

This is how it looks with initial configuration:

Create script:

 

EDIT 19.10.2018

Microsoft announced, that now you can parametrize also linked connections!

https://azure.microsoft.com/en-us/blog/parameterize-connections-to-your-data-stores-in-azure-data-factory/

Let’s get started (finally :P)


Preparations!

Go to your Azure Data Factory portal @ https://adf.azure.com/

Select Author button with pencil icon:

 

Creating server connections (Linked Services)

We can’t do anything without defining Linked Services, which are just connections to your servers (on-prem and cloud).

  1. Go to   and click 
  2. Find your database type, select and click 
  3. Give all needed data, like server ip/host, port, SID (Oracle need this), login and password.
  4. You can  if everything is ok. Click Finish to save your connection definition.
Some types of servers, such as PostgreSQL or MySQL, require separate .NET drivers. Check your server type here in Microsoft Docs and search for Prerequisites to match your scenario.

I have created three connections. Here are their names and server types:

 

Creating datasets

Creating linked services is just telling ADF what are connection settings (like connection strings).

Datasets, on the other hand, points directly to database objects.

BUT they can be parametrized, so you can just create ONE dataset and use it passing different parameters to get data from multiple tables within same source database 🙂

Source datasets

Source datasets don’t need any parameters. We will later use built-in query parametrization to pass object names.

  1. Go to   and click + and choose 
  2. Choose your datataset type, for example 
  3. Rename it just as you like. We will use name: “ORA”
  4. Set proper Linked service option, just like this for oracle database: 
  5. And that’s it! No need to set anything else. Just repeat these steps for every source database, that you have.

In my example, I’ve created two source datasets, ORA and PG

As you can see, we need to create also the third dataset. It will work as a source too, BUT also as a parametrizable sink (destination). So creating it is little different than others.

Sink dataset

Sinking data needs one more extra parameter, which will store destination table name.

  1. Create dataset just like in the previous example, choose your destination type. In my case, it will be Azure SQL Database.
  2. Go to , declare one String parameter called “TableName”. Set the value to anything you like. It’s just dummy value, ADF just doesn’t like empty parameters, so we have to set a default value.
  3. Now, go to , set Table as dynamic content. This will be tricky :). Just click “Select…”, don’t choose any value, just click somewhere in empty space. The magic option “Add dynamic content” now appears! You have to click it or hit alt+p. 
  4. “Add Dynamic Content” windows is now visible. Type: “@dataset().TableName” or just click “TableName” in “Parameters” section below “Functions”.
  5. The table name is now parameterized. And looks like this: 

 

Parametrizable PIPELINE with dynamic data loading.


Ok, our connections are defined. Now it’s time to copy data :>

 

Creating pipeline

  1. Go to you ADF and click PLUS symbol near search box on the left and choose “Pipeline“: 
  2. Reanme it. I will use “LOAD DELTA“.
  3. Go to Parameters, create new String parameter called ConfigTable. Set value to our configuration table name: load.cfg . This will simply parametrize you configuration source. So that in the future it would be possible to load a completely different set of sources by changing only one parameter :>
  4. In case you missed it, SAVE your work by clicking “Save All” if you’re using GIT or “Publish All” if not ;]

 

Creating Lookup – GET CFG

First, we have to get configuration. We will use Lookup activity to retrieve it from the database.

Bear in mind, that lookup activity has some limits. Currently, the maximum number of rows, that can be returned by Lookup activity is 5000, and up to 2MB in size. Also max duration for Lookup activity before timeout is one hour. Go to documentation for latest info and updates.
    1. Drag and drop  into your pipline
    2. Rename it. This is important, we will use this name later in our solution. I will use value “GET CFG“.
    3. In “Settings” choose 
    4. Now, don’t bother TableName set to dummy :> Just in “Use Query” set to “Query“, click “Add dynamic content” and type:
    5. Unmark “First row only“, we need all rows, not just first. All should look like this:

 

Creating Filters – ORA CFG & PG CFG

Now we have to split configs for oracle and PostgreSQL. We will use Filter activity on rows retrieved in “GET CFG” lookup.

  1. Drag and drop twice.
  2. Rename the first block to “ORA CFG“, second to “PG CFG“.
  3. Now go to “ORA CFG“, then “Settings“.
  4. In Items, click Add dynamic content and type:  @activity('GET CFG').output.value . As you probably guess, this will point directly to GET CFG output rows 🙂
  5. In Condition, click Add dynamic content and  type: @equals(item().SRC_name,'ORA') . We have to match rows for oracle settings. So we know, that there is a column in config table called “SRC_name“. We can use it to filter out all rows, except that with value ‘ORA’ 🙂 .
  6. Do the same with lookup activity “PG CFG“. Of course, change the value for a condition.

It should look like this:

Creating ForEach – FOR EACH ORA & FOR EACH PG

Now it’s time to iterate over each row filtered in separate containers (ORA CFG and PG CFG).

  1. Drag and drop two  blocks, rename them as “FOR EACH ORA” and “FOR EACH PG“. Connect each to proper filter acitivity. Just like in this example:  
  2. Click “FOR EACH ORA“, go to “Settings“, in Items clik Add dynamic content and type:  @activity('ORA CFG').output.value . We are telling ForEach, that it has to iterate over results returned in “ORA CFG”. They are stored in JSON array.
  3. Do this also in FOR EACH PG. Type:  @activity('PG CFG').output.value
  4. Now, you can edit Activities and add only “WAIT”  activity to debug your pipeline. I will skip this part. Just remember to delete WAIT block at the end of your tests.

 

Inside ForEach – GET MAX ORA -> COPY ORA -> UPDATE WATERMARK ORA

Place these blocks into FOR EACH ORA. Justo go there, click “Activities” and then 

Every row, that ForEach activity is iterating over, is accessible using @item() .

And every column in that row, can be reached just by using  @item().ColumnName .

Remember, that you can surround every expression in brackets @{ }  to use it as a string interpolation. Then you can concatenate it with other strings and expressions just like that:  Value of the parameter WatermarkColumn is: @{item().WatermarkColumn}

 

GET MAX ORA

  1. Go to “GET MAX ORA“, then Settings
  2. Choose your source dataset “ORA“, Use Query: “Query” and click Add dynamic content
  3. Type  SELECT MAX(@{item().WatermarkColumn}) as maxd FROM @{item().SRC_tab} . This will get a maximum date in your watermark column. We will use it as RIGHT BOUNDRY for delta slice.
  4. Check if  First row only is turned on.

It should look like this:

 

COPY ORA

Now the most important part :> Copy activity with a lot of parametrized things… So pay attention, it’s not so hard to understand but every detail matters.

Source

  1. In source settings, choose Source Dataset to ORA, in Use query select Query.
  2. Below Query input, click Add dynamic content and paste this:

Now, this needs some explanation 🙂

 

 

  • ORA CFG output has all columns and their values from our config.
  • We will use SRC_tab as table name, Cols as columns for SELECT query, WatermatkColumn as LastChange DateTime column name and WatermarkValue for LEFT BOUNDRY (greater than, >).
  • GET MAX ORA output stores date of a last updated row in the source table. So this is why we are using it as a RIGHT BOUNDRY (less than or equal, <=)
  • And the tricky thing, ORACLE doesn’t support implicit conversion from the string with ISO 8601 date. So we need to extract it properly with TO_DATE function.

So the source is a query from ORA dataset:

 

Sink

Sink is our destination. Here we will set parametrized table name and truncate query.

  1. Select 
  2. Parametrize TableName as dynamic content with value:  @{item().DST_tab}
  3. Also, do the same with Pre-copy script and put there:  TRUNCATE TABLE @{item().DST_tab}
As De jan properly noticed in comments, you are not obligated to use any Pre-copy script here. You can leave this box empty or run other commands like partitions switching.

It should look like this:

 

Mappings and Settings

All other things should just be set to defaults. You don’t have to parametrize mappings if you just copy data from and to tables that have the same structure.

Of course, you can dynamically create them if you want, but it is a good practice to transfer data 1:1 – both structure and values from source to staging.

 

UPDATE WATERMARK ORA

Now we have to confirm, that load has finished and then update previous watermark value with the new one.

We will use a stored procedure. The code is simple:

Create it on your Azure SQL database. Then use it in ADF:

  1. Drop  into project, connect constraint from COPY ORA into it. Rename as “UPDATE WATERMARK ORA” and view properties.
  2. In SQL Account set 
  3. Now go to “Stored Procedure”, select our procedure name and click “Import parameter”.
  4. Now w have to pass values for procedure parametrs. And we will also parametrize them. Id should be  @{item().id}  and NewWatermatk has to be:  @{activity('GET MAX ORA').output.firstRow.MAXD} .

 

And basically, that’s all! This logic should copy rows from all Oracle tables defined in the configuration.

We can now test it. This can be done with “Debug” or just by triggering pipeline run.

If everything is working fine, we can just copy/paste all content from “FOR EACH ORA” into “FOR EACH PG“.

Just remember to properly rename all activities to reflect new source/destination names (PG). Also, all parameters and SELECT queries have to be redefined. Luckily PostgreSQL support ISO dates out of the box.

Source code


Here are all components in JSON. You can use them to copy/paste logic directly inside ADF V2 code editor or save as files in GIT repository.

Below is source code for pipeline only. All other things can be downloaded in zip file in “Download all” at the bottom of this article.

Pipeline

 

Download all

IncrementalCopy_ADFv2.zip

 

116 thoughts on “Azure Data Factory V2 – Incremental loading with configuration stored in a table – Complete solution, step by step.

  1. Hi Michal,
    I have used all the convert functions you have said above like
    CONVERT(NVARCHAR(100), CONVERT(datetime, @{item().WatermarkValue}, 127), 120)
    but still am getting the error as
    {
    “errorCode”: “2100”,
    “message”: “Failure happened on ‘Source’ side. ErrorCode=SqlOperationFailed,’Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=A database operation failed with the following error: ‘Incorrect syntax near ‘T00:’.’,Source=,”Type=System.Data.SqlClient.SqlException,Message=Incorrect syntax near ‘T00:’.,Source=.Net SqlClient Data Provider,SqlErrorNumber=102,Class=15,ErrorCode=-2146232060,State=1,Errors=[{Class=15,Number=102,State=1,Message=Incorrect syntax near ‘T00:’.,},],'”,
    “failureType”: “UserError”,
    “target”: “GET_MIN_SRC_RTT”,
    “details”: []
    }
    My requirement here is am trying to read the DATE from the look up and the same I need to pass to the COPY data.

    Could you please help me here as am struck here?
    Regards,
    Mahasweta

    1. Hmm, we need to analyze what exactly is passed to the procedure, like Ashish analyzed in previous comments.
      And by the way, which SQL servers are you using? I mean for watermarks and as a source?

  2. Amazing Solution & thank for sharing Michal.
    I’m currently working on similar solution but I’m not using CopyActivity rather I’ve list of stored procedure with business logic in the database which need to be invoked dynamically and for that I’ve maintained similar Config table.
    In this config table, I’ve list of database stored procedure & ADF pipelines that need to be executed as a part of orchestration since there are dependencies on each others so i added pipelines names in config table too so it can follow the sequence when running in the loop, when i retrieve config table in LOOKUP activity i get both execution name & execution method(SP or ADf pipeline) so i can invoke 2 different activity 1) stored procedure 2) pipeline

    I can set expression for stored procedure activity and dynamically invoke respective stored procedure. However, I’m not able to set pipeline name dynamically using expression in Execute Pipeline activity and It’s not allow to invoke a pipeline dynamically by accepting parameter for pipeline reference name.

    I tried various option but it looks like invoke pipeline can’t pass dynamically with help of parameters

    Any idea, how to set pipeline name dynamically using expression in Execute Pipeline activity?

    Looking forward to hear from you.

    Thanks
    Nilesh

    1. Hi Nilesh.
      Sorry for a late reply. I’m a little busy these days..

      You are right. Pipeline execution can only be parametrized, if I can say like that – at parameters scope level 😐 There is no exposed way to define its name as parameter, as far as I can see.
      The only solution, that I can think of now, would be a master pipeline to execute all possible pipelines in your data factory, but limited by using proper activity – like SWITCH. You can then control the flow and decide to run only one pipeline depending on a passed parameter. It will take a lot of effort to do it, but unfortunately I’m not sure what else you can do here 😐

      So:
      1. Create MASTER pipeline from scratch, add parameter which will handle the pipeline name you want to execute
      2. Add switch activity, create expression to validate the value passed s parameter to the master pipeline
      3. Add as many cases as you have pipelines to run. Hardcode the value of your pipelines in case value
      4. Just add corresponding execute pipeline activity into each case activity, hardcode the pointer to the pipeline.

      And that’s it. You can now run master pipeline with parameter pointing to a proper pipeline.
      Also, if I were you, I would create an algorithm (like in powershell or python) to create automatically a native JSON block for this SWITCH just to give my script a list of all pipelines and it would generate something, that I can inject in portal or in git repo 🙂 Just a trick to not to waste my time for drag’n’dropping now and in the future 😉

      Hope this helps you somehow.
      Regards.
      m.

    1. That is ok if you do not want to track pipeline flow, since running REST works as a asynchronous process.
      In other words, you can’t control the run of the pipeline but for sure you can implement a logic that will check the status periodically by firing another rest call.
      Also, bear in mind, that in case of web activity: “The activity will timeout at 1 minute with an error if it does not receive a response from the endpoint.” https://docs.microsoft.com/en-us/azure/data-factory/control-flow-web-activity#type-properties
      It’s just an internal timeout in ADF and it happened for me two or three times, that Azure API did not respond in one minute 😐 (not particularly in ADF API, but anyway). So maybe just do not forget to implement some retry logic 🙂

      So if it does meet you requirements, then I’m happy that you figured it out 🙂 Thanks for the update!

  3. Hi Michael, I am very grateful for your article, it helped me a lot because I had never done an incremental load and I had no idea how to do it, nor was it a configuration table. I hope you continue to upload important content.
    Thanks in advance.

  4. Hi Michal, thank you for the post.
    I’m doing some tests and researches about build a metadata layer for pipelines and your post it’s very helpful.
    Unfortunately, my source systems doesn’t have an update_date column on tables, so, I will need to build incremental load using the transactions date fields, like OrderDate, and I will need to reprocess, for example, the last month, every day, to try keep the data on Azure up to date.
    Would you have any advice about this requirement?
    Have you already worked in a similar one?

    Thanks a lot!
    Renato Freitas

    1. Hi Renato!
      Each application can have potentially different date methods. It is important to know the volume of data that changes each day and how the order date changes too. So you need to make sure that there are no traps behind such a mechanism and the pipeline will do everything as it should.

      Also, remember that you should always try to perform the tasks at the lowest cost. More data means longer operation time and more information flowing through the network. And thus it increases costs. So if the total costs of downloading the data daily, but always asking for the last month, are not higher than the cost of tracking mechanism implementation, e.g. Change Data Capture, then this is a good solution. Otherwise, I would like to think about whether it is worth to burn money. The cloud teaches you the right, minimalist approach, and requires extensive knowledge of costs.

      Regards,
      m.

  5. Thank you so much Michal,
    I am using azure sql database.
    I have copy data and data flow in my pipeline, I want to use the variable in my sink in the data flow.
    My steps:
    1. Create variable on the pipeline

    NAME TYPE DEFAULT VALUE
    TimeVal String empty

    then tried to reference it in my query but not sure the syntax is right

    2. The referencing is the problem, can you write the right syntax please ?
    update Life_master set last_upd_dt =(@pipeline().Pipeline.TimeVal) where job_id = 2 ?

    It looks like I am missing some steps,
    can you please give me an example of the whole process including setting up the global timestamp, referencing it. Thanks,

    Hope

    1. Hmm, ok.

      You need to read this article first, as it is a different case and you need to parametrize a data flow and pass a value from the pipeline:
      https://docs.microsoft.com/en-us/azure/data-factory/parameters-data-flow

      Anyway, you need to follow a very simple pattern in case of passing date from a variable/parameter to the datetime (and other) column:
      – use brackets (As you always do when passing date as a string into table)
      – extract the proper date as you need, from your parameter/variable, using proper functions

      For example, I have a simple table, like yours (open all links in a new tab):
      http://sql.pawlikowski.pro/wp-content/uploads/2020/07/01.jpg

      I’m using ‘Set Variable’ activity to assign dynamic content “utcnow()” into pipeline variable “TimeVal”.
      The returned result of this function (and activity) is:
      http://sql.pawlikowski.pro/wp-content/uploads/2020/07/02.jpg

      Now, to update a value in the database normally I would use a stored procedure.
      But this time I will use a little trick to make this faster.
      ADF does not have TSQL script activity as SSIS do, so we can use Lookup activity and return dummy result (as it needs something) and run some logic before it.
      Just remember to use procedure in your case, ok? ;D

      And the dynamic content, it looks like this:

      http://sql.pawlikowski.pro/wp-content/uploads/2020/07/03.jpg

      The code is:
      update Life_master set last_upd_dt ='@{formatDateTime(variables('TimeVal'), 'yyyy-MM-dd HH:mm:ss')}' where job_id = 2;
      SELECT 0 as dummy

      You can specify more details on the date, like milliseconds accordingly to the .NET custom date format specification:
      https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings#ssSpecifir

      And the final result is:
      http://sql.pawlikowski.pro/wp-content/uploads/2020/07/04.jpg

      So, you can prepare a variable, just like I did in the dynamic content, using functions, then you can pass it directly to the data flow.
      On the other hand, I’m curious why you need to set those dates inside data flow, not outside, directly in the pipeline. It’s just a metadata step, but I guess it always depends on a scenario 😐

      I hope I helped you.

      1. Thank you Michal,

        The reason why I am updating the date in the sink data flow is:
        There is Last Updated date column in the source at the beginning of my pipeline and wanted to to update that at the sink after all the transformations. However, I don’t want to loss any incoming data between this process. As a result, I want to capture the time the data flow strats at the source and wanted to use the time variable in my update query at the sink. In that case, if my date flow transformation takes 5 minutes to finish, all the incoming data at that time interval will not be lost.

        I will try to use your approach and let you know. However, For some internal reason ,I can not use stored procedures in my data flow. Do you think this is the right approach?
        Let me know your thoughts.
        Regards,
        Hope

        1. Hi Hope.
          Hmm, I’m feeling that I do not get it right but anyway, few points:

          – in case of changing anything to the column values, during the transformation process, just don’t forget that there is a derived transformation which will bring anything you want to save to your sink data, as a newly created column or replace the old one:
          https://docs.microsoft.com/en-us/azure/data-factory/data-flow-derived-column

          – well, if you can’t create a procedure inside the database, the lookup trick is one of the workarounds. It does work, but of course is just not a good practice (as any “modifying” process hardcoded into external tools, like Azure Data Factory, can be harmful in many ways ;] tracking changes, maintaining the logic, etc., but that’s just a rule of thumb, nothing more)

          Good luck 🙂

          1. Hello Michal,
            As I am new to Azure ADF, this has been very helpful.
            I really appriciate your support and quick replies. I am now using your template and working on it.
            Quick question,

            I have a data column called ACTIVE with a data of 0 and 1 in my source. I want to transform these to Y and N in my data flow and used the replace function and created a derived column to do that. However, it is changing all the data to Y or N.
            Here is my step using replace function:
            replace(‘1’, ‘1’, ‘Y’) —to change it to Y and
            replace(‘0’, ‘0’, ‘N’) — to change it to N

            what is the problem with that and how can I correct to make both changes at the same time?

            Regards,
            Hope

  6. I have SOURCE like
    HOST = @item().SRC_HOST
    DB = @item().SRC_DB
    SCHEMA = @item().SRC_SCHEMA
    TABLE = @item().SRC_TABLE

    How can I select table using all above 4 parameter to get accurate table data. like SELECT * FROM @{item().SRC_HOST}].[@{item().SRC_DB}].[@{item().SRC_SCHEMA}].[@{item().SRC_TABLE}]

    I have to write SELECT because i have additional column TARGET table (TRG_), and via BULK INSERT i am not able to do TABLE copy. Below JSON code

    {
    “name”: “STG_AGILYSYS_test”,
    “properties”: {
    “activities”: [
    {
    “name”: “forEachShip”,
    “type”: “ForEach”,
    “dependsOn”: [
    {
    “activity”: “lookupShip”,
    “dependencyConditions”: [
    “Succeeded”
    ]
    }
    ],
    “userProperties”: [],
    “typeProperties”: {
    “items”: {
    “value”: “@activity(‘lookupShip’).output.value”,
    “type”: “Expression”
    },
    “activities”: [
    {
    “name”: “SQLtoSQLDW”,
    “type”: “Copy”,
    “dependsOn”: [],
    “policy”: {
    “timeout”: “7.00:00:00”,
    “retry”: 0,
    “retryIntervalInSeconds”: 30,
    “secureOutput”: false,
    “secureInput”: false
    },
    “userProperties”: [],
    “typeProperties”: {
    “source”: {
    “type”: “SqlServerSource”,
    “sqlReaderQuery”: “select \n chk_ftr_line1,\nchk_ftr_line2,\nchk_ftr_line3,\nchk_hdr_line1,\nchk_hdr_line2,\nchk_hdr_line3,\ndata_control_group_id,\ndefault_table_layout_id,\ndoc_lines_advance,\nent_id,\nmax_doc_lines_page,\nmin_rcpt_lines_page,\nprint_by_rev_cat_flag,\nprofit_center_id] int,\nprofit_center_name,\nprofit_ctr_abbr1,\nprofit_ctr_abbr2,\nsales_tippable_flag,\nstore_id,\nmerchant_id,\nbypass_CC_agency_threshold_amount,\nbypass_CC_voice_auth_threshold_amount,\nbypass_CC_printing_threshold_amount,\nprimary_language_id,\nsecondary_language_id,\ntip_max_percent,\ntip_enforcement_code_id,\nprofit_center_desc,\nsource_property_code,\npole_display_open,\npole_display_closed,\nrow_version \nfrom [@{item().SRC_SCHEMA}].[@{item().SRC_TABLE}]”,
    “queryTimeout”: “02:00:00”
    },
    “sink”: {
    “type”: “SqlDWSink”,
    “preCopyScript”: “TRUNCATE table STG_AGILYSYS_CT.temp_Profit_Center_Master”,
    “disableMetricsCollection”: false
    },
    “enableStaging”: false,
    “translator”: {
    “type”: “TabularTranslator”,
    “typeConversion”: true,
    “typeConversionSettings”: {
    “allowDataTruncation”: true,
    “treatBooleanAsNumber”: false
    }
    }
    },
    “inputs”: [
    {
    “referenceName”: “AgilysysSqlServer”,
    “type”: “DatasetReference”,
    “parameters”: {
    “HOST”: {
    “value”: “@item().SRC_HOST”,
    “type”: “Expression”
    },
    “DB”: {
    “value”: “@item().SRC_SCHEMA”,
    “type”: “Expression”
    },
    “TABLE”: {
    “value”: “@item().SRC_TABLE”,
    “type”: “Expression”
    }
    }
    }
    ],
    “outputs”: [
    {
    “referenceName”: “SqlDWDataAgilysys”,
    “type”: “DatasetReference”,
    “parameters”: {
    “tableName”: {
    “value”: “@item().TRG_TEMP_TABLE”,
    “type”: “Expression”
    },
    “schemaname”: {
    “value”: “@item().TRG_SCHEMA_NAME”,
    “type”: “Expression”
    }
    }
    }
    ]
    }
    ]
    }
    },
    {
    “name”: “lookupShip”,
    “type”: “Lookup”,
    “dependsOn”: [],
    “policy”: {
    “timeout”: “7.00:00:00”,
    “retry”: 0,
    “retryIntervalInSeconds”: 30,
    “secureOutput”: false,
    “secureInput”: false
    },
    “userProperties”: [],
    “typeProperties”: {
    “source”: {
    “type”: “SqlDWSource”,
    “sqlReaderQuery”: “SELECT SRC_SHIP_CODE, SRC_HOST, SRC_SCHEMA, SRC_TABLE, \nsubstring(TRG_TEMP_TABLE,1,charindex(‘.’, TRG_TEMP_TABLE)-1) as TRG_SCHEMA_NAME, \nsubstring(TRG_TEMP_TABLE, charindex(‘.’, TRG_TEMP_TABLE)+1,100) \n as \n TRG_TEMP_TABLE \nFROM \n STG_CONTACT_TRACING.ETL_LOAD_DETAIL \nWHERE SRC_STATUS = ‘A’ \nAND SRC_NAME = ‘AGILYSYS’;”,
    “queryTimeout”: “02:00:00”
    },
    “dataset”: {
    “referenceName”: “devEtlLoadDetail”,
    “type”: “DatasetReference”
    },
    “firstRowOnly”: false
    }
    }
    ],
    “folder”: {
    “name”: “Kiana”
    },
    “annotations”: []
    }
    }

    1. Hi Vikas.

      Please provide the error message that you have.
      The SELECT statement is missing one opening bracket next to the host name, but everything else looks properly. Of course remember to add it as a “dynamic content” not just by pasting it to the query field.

      This is a fully qualified name notation, and you can reference local and remote data with it. For now I can’t tell you what is wrong.

      1. My question was

        I have dynamic SOURCE like
        HOST = @item().SRC_HOST
        DB = @item().SRC_DB
        SCHEMA = @item().SRC_SCHEMA
        TABLE = @item().SRC_TABLE

        In want to use QUERY, which will use the dynamic SELECT query
        How can I select table using all above 4 parameter to get accurate table data. like

        SELECT * FROM @{item().SRC_HOST}].[@{item().SRC_DB}].[@{item().SRC_SCHEMA}].[@{item().SRC_TABLE}]

        I am doing this because I have 39 source system having same table, which i will load in one Target table, Also I want to put CDC logic.

        Getting error when doing so
        {
        “errorCode”: “2200”,
        “message”: “Failure happened on ‘Source’ side. ‘Type=System.Data.SqlClient.SqlException,Message=Must declare the table variable \”@item\”.,Source=.Net SqlClient Data Provider,SqlErrorNumber=1087,Class=15,ErrorCode=-2146232060,State=2,Errors=[{Class=15,Number=1087,State=2,Message=Must declare the table variable \”@item\”.,},],'”,
        “failureType”: “UserError”,
        “target”: “SQLtoSQLDW”,
        “details”: []
        }

        CODE BELOW
        {
        “name”: “STG_AGILYSYS_CONTACT_TRACING_ORDER_HEADER”,
        “properties”: {
        “description”: “This job is used to migrate Delta changes (SCD type 1 ) from 39 ships data to Synapse SQL DW for ORDER_HEADER table”,
        “activities”: [
        {
        “name”: “forEachShip”,
        “type”: “ForEach”,
        “dependsOn”: [
        {
        “activity”: “lookupShip”,
        “dependencyConditions”: [
        “Succeeded”
        ]
        }
        ],
        “userProperties”: [],
        “typeProperties”: {
        “items”: {
        “value”: “@activity(‘lookupShip’).output.value”,
        “type”: “Expression”
        },
        “isSequential”: false,
        “activities”: [
        {
        “name”: “SQLtoSQLDW”,
        “type”: “Copy”,
        “dependsOn”: [],
        “policy”: {
        “timeout”: “7.00:00:00”,
        “retry”: 0,
        “retryIntervalInSeconds”: 30,
        “secureOutput”: false,
        “secureInput”: false
        },
        “userProperties”: [],
        “typeProperties”: {
        “source”: {
        “type”: “SqlServerSource”,
        “additionalColumns”: [
        {
        “name”: “ship_cd”,
        “value”: {
        “value”: “@item().SRC_SHIP_CODE”,
        “type”: “Expression”
        }
        }
        ],
        “sqlReaderQuery”: “select * from \t\n@item().SRC_HOST.@item().SRC_SCHEMA.\t\n@item().SRC_TABLE”,
        “queryTimeout”: “02:00:00”
        },
        “sink”: {
        “type”: “SqlDWSink”,
        “disableMetricsCollection”: false
        },
        “enableStaging”: false,
        “translator”: {
        “type”: “TabularTranslator”,
        “typeConversion”: true,
        “typeConversionSettings”: {
        “allowDataTruncation”: true,
        “treatBooleanAsNumber”: false
        }
        }
        },
        “inputs”: [
        {
        “referenceName”: “AgilysysSqlServer”,
        “type”: “DatasetReference”,
        “parameters”: {
        “HOST”: {
        “value”: “@item().SRC_HOST”,
        “type”: “Expression”
        },
        “DB”: {
        “value”: “@item().SRC_SCHEMA”,
        “type”: “Expression”
        },
        “TABLE”: {
        “value”: “@item().SRC_TABLE”,
        “type”: “Expression”
        }
        }
        }
        ],
        “outputs”: [
        {
        “referenceName”: “SqlDWDataAgilysys”,
        “type”: “DatasetReference”,
        “parameters”: {
        “tableName”: {
        “value”: “@item().TRG_TEMP_TABLE”,
        “type”: “Expression”
        },
        “schemaname”: {
        “value”: “@item().TRG_SCHEMA_NAME”,
        “type”: “Expression”
        }
        }
        }
        ]
        }
        ]
        }
        },
        {
        “name”: “lookupShip”,
        “type”: “Lookup”,
        “dependsOn”: [],
        “policy”: {
        “timeout”: “7.00:00:00”,
        “retry”: 0,
        “retryIntervalInSeconds”: 30,
        “secureOutput”: false,
        “secureInput”: false
        },
        “userProperties”: [],
        “typeProperties”: {
        “source”: {
        “type”: “SqlDWSource”,
        “sqlReaderQuery”: “TRUNCATE table STG_AGILYSYS_CT.Order_Header_Temp\n\nSELECT SRC_SHIP_CODE, SRC_HOST, SRC_SCHEMA, SRC_TABLE, \nsubstring(TRG_TEMP_TABLE,1,charindex(‘.’, TRG_TEMP_TABLE)-1) as TRG_SCHEMA_NAME, \nsubstring(TRG_TEMP_TABLE, charindex(‘.’, TRG_TEMP_TABLE)+1,100) \n as \n TRG_TEMP_TABLE \nFROM \n STG_CONTACT_TRACING.ETL_LOAD_DETAIL \nWHERE SRC_STATUS = ‘A’ \nAND SRC_NAME = ‘AGILYSYS’\nand SRC_TABLE=’Order_Header’;”,
        “queryTimeout”: “02:00:00”
        },
        “dataset”: {
        “referenceName”: “devEtlLoadDetail”,
        “type”: “DatasetReference”
        },
        “firstRowOnly”: false
        }
        },
        {
        “name”: “SP_Agilysys_Contact_Tracing”,
        “type”: “SqlServerStoredProcedure”,
        “dependsOn”: [
        {
        “activity”: “forEachShip”,
        “dependencyConditions”: [
        “Succeeded”
        ]
        }
        ],
        “policy”: {
        “timeout”: “7.00:00:00”,
        “retry”: 0,
        “retryIntervalInSeconds”: 30,
        “secureOutput”: false,
        “secureInput”: false
        },
        “userProperties”: [],
        “typeProperties”: {
        “storedProcedureName”: “[dbo].[sp_Agilysys_Contact_Tracing]”,
        “storedProcedureParameters”: {
        “table_name”: {
        “value”: {
        “value”: “@activity(‘lookupShip’).output”,
        “type”: “Expression”
        },
        “type”: “String”
        }
        }
        },
        “linkedServiceName”: {
        “referenceName”: “DevSynapse”,
        “type”: “LinkedServiceReference”
        }
        }
        ],
        “folder”: {
        “name”: “Kiana”
        },
        “annotations”: []
        }
        }

Leave a Reply