When a custom query is used for a copy activity, the query gets cut off and does not display the entire query. There are actually three issues that occur currently.

1) The entire query should be visible or placed in a text area with read only properties.

2) There should be a copy button on the query so that we can execute the exact query that was used. This is for troubleshooting errors that occur.

3) Make the initial textbox that is used for the input of the query larger and add in formatting functions so viewing potential syntax errors are easier.

We have activity dependencies today, but they are always logical AND. If we have Activity1 -> Activity 2 -> Activity3 and we want to say if any of these activities fail, run activity 4, it isn't straight forward. In SSIS, we can choose an expression and choose whether we need one or all conditions to be true when there are multiple constraints. We need similar functionality here. It can be achieved with a bit of creativity (repeat the failure activity as the single failure path after each of the original activities use the If Condition to write logic that would denote failure in a previous activity), but it's more convoluted than it needs to be.

Setting up the timing of a Trigger, you need to know how far away from UTC you are so you can specify the right time. That value changes for those of us that observe Daylight Savings Time.
The dialog box for setting up a Trigger Schedule should instead have the following three inputs:
1) the LOCAL time you want it to run
2) the Time Zone
3)Adjust for DST.

THAT is the information people have at their disposal.
To adjust for DST, I must EDIT all my Triggers manually to ensure they run at the right hour of the day when we change over to/from DST.

I downloaded the latest version of SQL Server Data Tools 2017, which has component Microsoft SQL Server Integration Services Designer 15.0.X.Y

All my deployments to SSIS Integration Runtime (hosted using Azure SQL Server) failed when using Script Task saying "Cannot load script for execution".

I first thought it'd be a problem in my laptop, but then I benchmarked with one of my peers, he downloaded the same SSDT version and his packages got the same error.

Then I downloaded the earliest possible version of SSDT 2017 (15.6.X) which includes component Microsoft SQL Server Integration Services Designer 14.0.X.Y.

Packages worked fine after that.
Thank you.

A copy activity will fail if if my source has more columns than my destination. I would like to use the implicit mapping (let data factory match on column name) but have it not fail if a source column has no matching destination. For example, if I am copying from a text file in ADLS to a table in Azure SQL DB and my source file has 200 columns but I only need 20, I don't want to have to bring in all 200 fields. I also don't want to have to map them all. Instead of failing, ADF should just copy over the ones that match. Throwing a warning would be fine, but even that seems unnecessary. If fields are not mapped, we'll check the output and make adjustments to column names in the destination. But forcing me to map source and destination makes it so that I can't feed in file/table names through a for each loop and use dynamic (parameterized) datasets.

Hi,

I am searching for the feature in data factory for databricks activity, suppose there is pipeline and in that pipeline there are multiple databricks activity, as of now i can make use of new job cluster to execute all the databricks activities but by doing this spin up the cluster and terminate the cluster for each activity is taking lot of time, i would like to have a functionality where i can create a cluster at the begining of the pipeline and all activities make use of the existing cluster and at the end we can terminate the cluster. there is other option as well to reuse the existing cluster but start and stop and use the cluster in the pipeline would be great and added advantage