Brandon Ledbetter

My feedback

  1. 501 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Brandon Ledbetter commented  · 

    I am currently using the Lookup activity to perform commands like creating a staging table, adding a table partition, switching partitions between the staging table and the target table, etc. I simply end the SQL statement in the Lookup activity with "select 1;" so that it is satisfied that it has a result set (that my pipeline does not use). I opened an Azure support ticket to find out if this was considered a legitimate use of the Lookup activity, and their answer was "no, it hasn't been tested for that". I've also mentioned this to a Technical Account Manager, and his feedback was that he has several customers using the Lookup activity in this way at a large scale. So we will probably proceed with caution, rather than have to maintain stored procs as a separate CI pipeline. But it would be great to have official support with an "Execute command" activity that is officially supported for this use case.

    Brandon Ledbetter supported this idea  · 
  2. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon Ledbetter shared this idea  · 

Feedback and Knowledge Base