Hi All,
I have VS 2022 installed along with SQL server data tools enabled. I also installed SQL Server integration service project 2022 downloaded and installed. Sql server 2019 enterprise version is already installed. I could not find dtexecui.exe utility tool any where in the machine. What am I missing ? When I opened SQL server installation center , I don't find any option for Integration service. Does that the reason behind no integration server? How do I get the utility tool?
Regards,
Prakash
Thanks,
Charmer
January 31, 2024 at 11:34 am
In VS2022, if you go to Extensions/Installed/All, do you see the following?
'SQL Server Integration Services Projects 2022'
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 31, 2024 at 12:08 pm
OK, good. So what is it that you are not able to do, exactly?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 31, 2024 at 12:46 pm
OK, good. So what is it that you are not able to do, exactly?
Hi Phil,
I just installed SQL Server 2019 Management Studio and found DTExecUI.exe. When attempting to use this utility to run a package in a file system, I receive an error stating, 'To run an SSIS package outside of SQL Server Data Tools, you must install Standard Edition (64-bit) of Integration Services or higher.'
The primary objective is to execute SSIS packages from an MS Access database via a button event for my client. Initially, I considered referencing the DTExec path in VBA code to execute the package. Additionally, I explored deploying the package to the Integration Services Catalog, using a stored procedure to call the package and integrating SQL commands in the VBA code. However, I encountered another challenge related to 'Create a master key or open the master key in a session.'.
Thanks,
Charmer
Having Access run a stored proc to execute a package deployed to SSISDB is the way to go. Any other way is likely to violate software licensing.
If you don't currently use SSISDB, it may be possible to delete it and recreate an empty one. Though there is probably more to it than that – needs to be researched.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 31, 2024 at 1:19 pm
Having Access run a stored proc to execute a package deployed to SSISDB is the way to go. Any other way is likely to violate software licensing.
If you don't currently use SSISDB, it may be possible to delete it and recreate an empty one. Though there is probably more to it than that – needs to be researched.
I get your point. Let me see what happens when I delete it. 🙂
Thanks,
Charmer
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply