CODEWITHSUNDEEP
sql-servermergessis
Sarah
Sarah

Reputation: 1293

SSIS merge join

We have SQL Server 2012 on our test servers and I have developed a SSIS package in 2017 with Deployment Target Version set to 2012 on my local machine.

Within the package I have a mergeJoin object. The entire package runs nicely on my local machine, when I set it on test machine which via SQL server agent on 2012, it gives an error saying

To run a SSIS package outside of SQL Server Data Tools you must install Merge Join of Integration Services or higher

Integration services is installed on SQL Server 2012.

Is there a solution to this or if there is a workaround using merge join object, if I can replace with another object.. please suggest.

Upvotes: 3

Views: 358

Answers (2)

Sarah
Sarah

Reputation: 1293

Ok turned out that the test machine didn't have SSIS installed. Confusion is that there are other jobs using SSIS under SQL server agent that are running successfully on test, just this one with the merge Join is failing.

My conclusion is packages will run under SQL job agent that are simple without heavy work on machine that don't have SSIS installed, but in-order for package to run merge join or "not too straight forward" objects, SSIS has to be installed for a package to run.

Upvotes: 2

Jeremy J.
Jeremy J.

Reputation: 727

In regards to not using a Merge Join, if the data sources you are joining are from the same relational database, then you could just use a JOIN in your source query instead of using a merge join. If the sources you are joining are from flat files or different databases, then you need to load the data to a staging area first, and then create a new data flow task where you could use a JOIN in your source query to join the data sources.

Upvotes: 0

Related Questions