client tools sdk missing from sql server 2022 setup feature selection

Question

Looking to run SSIS pkgs from my local machine in c# and my searching says I need the "Client Tools SDK" for SQL Server.

Been googling for a while (>2hours) and following threads of which this one seemed promising :
https://social.msdn.microsoft.com/Forums/en-US/782b92bc-d1d4-403b-8a3b-30c168160b2f/client-connectivity-tools?forum=sqlsetupandupgrade

it showed the following screen at that link:

After installing SSIS which I was instructed to by another search, my Feature Selection does not have "Client Tools SDK" shown below:

Kinda dead in water atm.

Looking forward to your responses :)

Mike

Answer 1

Hi Yitzhak,

My use case is exactly to NOT run them on the SQL Server but to call the SSIS pkgs directly from my local machine.

from my earlier post:

"I'm unable to run it that way (on the sql server) as the ssis pkg is used to transfer information from two different servers, staging -> production, and the production server is not allowed to access a staging server directly and DBA policy forbids linking the servers."

I want to install the SDK on my machine, only I've not been able to find the dll that was mentioned in the Microsoft posts I referenced.

I'm hoping that you have a different suggestion ?

Mitch

Answer 2

Hi @Mitch,

Here is an official Microsoft documentation on the subject:

https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-run-dotnet?view=sql-server-ver16

This page provides information on how to install SMO for use by applications and the system requirements to use SMO.

https://learn.microsoft.com/en-us/sql/relational-databases/server-management-objects-smo/installing-smo?view=sql-server-ver16

Answer 3

HI Yitzhak,

Thank you for the response.

I did happen upon the link you sent earlier in my search, however, the code snippet in it seems to run the package from the SQL Server that the pkg was deployed on (it uses a connection to the SQL Server). I'm unable to run it that way as the ssis pkg is used to transfer information from two different servers, staging -> production, and the production server is not allowed to access a staging server directly and DBA policy forbids linking the servers.

I had previous accomplished this by running the pkg in visual studio from my local machine, however this is what I need to access via c# to automate.

The code that I found that I believe accomplishes this I found at this link:

https://learn.microsoft.com/en-us/sql/integration-services/run-manage-packages-programmatically/loading-and-running-a-local-package-programmatically?redirectedfrom=MSDN&view=sql-server-ver16

But this seems to require the Client Tools SDK (afaik from the searching), which led me down the rabbit hole I'm still in :)

I'm hoping this clarifies a bit more and that you might have another suggestion.

Mike

Answer 4

This is a link I started with while trying to get to "Client Tools SDK":

https://learn.microsoft.com/en-us/sql/integration-services/install-windows/install-integration-services?view=sql-server-ver16

Mike

Answer 5

@Mitch,

You can keep SSIS projects and packages in the SSIS Catalog on the server. They are callable from c# code via a stored procedure call. This way you don't need to install any additional SDKs and APIs on your machine.

Check it out here: https://learn.microsoft.com/en-us/sql/integration-services/ssis-quickstart-run-tsql-vscode?view=sql-server-ver16