SSIS tasks installation

Question

SSIS tasks installation

spaghettidba

SSC Guru

Points: 105732
More actions
May 2, 2014 at 9:43 am

#290956
I'm seeking help from a real SSIS expert, which I'm not to any extent.
I recently developed an open source project called "Extended TSQL Collector" and can be found here https://extendedtsqlcollector.codeplex.com
The purpose of the project is to provide a new collector type to the built-in Data Collector collectors to work around some limitations.
Basically, a collector type is made of two SSIS packages: one to collect the data and one to upload it to the MDW database.
In my case, both packages are invoking an external application which takes care of everything. To invoke the application, I use an execute process task.
Everything works fine when the SSIS components are installed, but fails when SSIS is missing, which is understandable to some extent.
What puzzles me is that the other built-in collector types work flawlessly even if SSIS is not installed.
- Which tasks are installed with the database engine services and don't need to be installed with SSIS?
- Is there a way to install the Execute Process Task other than installing SSIS?
- Can I programatically check if a SSIS task is installed?
-- Gianluca Sartori

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Eirikur Eiriksson SSC Guru Points: 182881 More actions · Answer 1

Chio, you could compare the installation logs from the different instances to track down the difference. I'll try out your component on a vanilla system and let you know the results.

😎

spaghettidba SSC Guru Points: 105732 More actions · Answer 2

Thanks for the hint.

Actually, everything in %programfiles%\Microsoft SQL Server\110\DTS\Tasks is missing in a system without SSIS components.

Searching the registry I found that each task has many entries and I suppose that they have to be registered.

-- Gianluca Sartori

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 3

I would assume that if you want to run an SSIS package, SSIS needs to be installed.

What exactly do you mean with this?

other built-in collector types work flawlessly even if SSIS is not installed.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

spaghettidba SSC Guru Points: 105732 More actions · Answer 4

All the built-in collector types use SSIS packages to collect and upload data, but you don't have to install SSIS to make them work.

Looking in the installation folder of SQL Server, I see some tasks DLLs. The "Execute Process Task" is not there.

I suppose that the tasks needed for the built-in collectors and the maintenance plans are installed with the "database engine" components, while all the other tasks are installed only with the SSIS components.

-- Gianluca Sartori

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 5

spaghettidba (5/5/2014)
All the built-in collector types use SSIS packages to collect and upload data, but you don't have to install SSIS to make them work.
Looking in the installation folder of SQL Server, I see some tasks DLLs. The "Execute Process Task" is not there.
I suppose that the tasks needed for the built-in collectors and the maintenance plans are installed with the "database engine" components, while all the other tasks are installed only with the SSIS components.

Ah yes, you have the "basic" components needed for maintenance plans and the import/export wizard, but anything beyond that needs the installation of SSIS. Is the Execute Process Task needed? Can you start the process with a batch file?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

spaghettidba SSC Guru Points: 105732 More actions · Answer 6

Thanks for the input.

I need the execute process task, unless there's another way to execute a process. How would a batch file help me here?

-- Gianluca Sartori

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 7

A batch file can start a process, just like an Execute Process Task.

You have to call the batch file out of SSIS though.

How is the SSIS package currently started?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

spaghettidba SSC Guru Points: 105732 More actions · Answer 8

I see what you mean...

It is started by a process named DCEXEC.EXE which controls the Data Collector collection sets.

DCEXEC is invoked by a SQL Agent job generated automatically by the Data Collector configuration.

I could change the jobs directly, but it wouldn't reflect the changes in the Data Collector configuration and it would be overwritten by changes in the Data Collector config window.

-- Gianluca Sartori