Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Jason Horner

My feedback

  1. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Horner commented  · 

    Agreed, adding these properties would allow much simpler conditional processing such as skipping zero length files or files that were created outside of a date range or where the MD5 hash is different by using the filter activity. These are all valid use cases and should be supported.

  2. 0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  3. 33 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Synapse Analytics » SQL/Polybase  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner supported this idea  · 
  4. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Synapse Analytics » SQL/Loading  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  5. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Synapse Analytics » SQL/T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  6. 100 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Jason Horner commented  · 

    You should be able to link an External Table to a delta Lake with full CRUD support. This is a major Adoption blocker for Serverless versus Azure Databricks

    Jason Horner supported this idea  · 
  7. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Synapse Analytics » SQL/T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  9. 108 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  6 comments  ·  Azure Synapse Analytics » SQL/T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Horner commented  · 

    Agreed this should support functions like SYSDATETIME() and SUSER_NAME() too

  10. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Horner commented  · 

    i just noticed this isn't in the synapse space which may be why it isn't getting as much traction it might be best to close this issue and vote for it here: https://feedback.azure.com/forums/307516-azure-synapse-analytics/suggestions/42167926-merge-doesn-t-support-a-replicated-table-with-iden

    An error occurred while saving the comment
    Jason Horner commented  · 

    I really don't understand how this feature got to public preview without supporting a merge statement that targets a table that has an identity property defined and is replicated.

    this would be the primary use case for using merge within synapse would be to implement upsert pattern with a identity surrogate key against a replicated table.

  11. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Synapse Analytics » SQL/Loading  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  12. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Synapse Analytics » SQL/T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  13. 725 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Horner commented  · 

    there are two ways to accomplish this using the stored procedure activity (which doesn't support resultsets or return values) or us the lookup activity which does... of course the current set of DB's is limited.

  14. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  15. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  16. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  17. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  18. 73 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Horner commented  · 

    Cool it looks like this is supported now!!!!

    Jason Horner supported this idea  · 
    An error occurred while saving the comment
    Jason Horner commented  · 

    Both Azure Analysis Services, and SQL Data Warehouse REST API's (As Well as numerous other Azure REST API's) Require the PATCH Command to Scale the service.

    Additionally, Many other REST API management scenarios would be unlocked by supporting this. Creating an Azure Function or Batch Service is Overkill for this use case and creates an unneeded coding effort that is orthogonal to solving the business problem at hand. (Scaling or modifying the sate of a resource)

  19. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner shared this idea  · 
  20. 38 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Azure Synapse Analytics » SQL/T-SQL  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Horner supported this idea  · 
← Previous 1

Feedback and Knowledge Base