Executing packages from ASP.Net

I just want to confirm my thinking here.

-I have a server (serverA) which has SSIS installed and some .dtsx files sitting in a shared folder.
-I have a server (serverB) which is running some ASP.Net apps.

One of my ASP.Net apps on serverB needs to execute the packages stored on serverA.

Am I correct in thinking that I need SSIS installed on serverB or is there another way?

-Jamie

You need to install SSIS on machine where the package is run.

So if you need to run the package on serverB - yes, you need
to install SSIS on serverB.

If you can run the package on serverA - you don't need SSIS
on serverB. Instead, run the package remotely.

E.g. you can create an Agent job (without schedule) that
executes on serverA and then run it on demand from serverB.

Thanks,
Michael.|||Thanks for the confirmation Michael.|||

I have done as you suggested here and created an Agent job ... How do I call for the job in my vb code in the application? (Both SSIS & Application are on the same server)

Wes

|||

Wes Linz wrote:

I have done as you suggested here and created an Agent job ... How do I call for the job in my vb code in the application? (Both SSIS & Application are on the same server)

Wes

Use sp_start_job SQL stored procedure (see syntax in Books Online)

sql

Executing packages from ASP.Net

I just want to confirm my thinking here.

-I have a server (serverA) which has SSIS installed and some .dtsx files sitting in a shared folder.
-I have a server (serverB) which is running some ASP.Net apps.

One of my ASP.Net apps on serverB needs to execute the packages stored on serverA.

Am I correct in thinking that I need SSIS installed on serverB or is there another way?

-Jamie

You need to install SSIS on machine where the package is run.

So if you need to run the package on serverB - yes, you need
to install SSIS on serverB.

If you can run the package on serverA - you don't need SSIS
on serverB. Instead, run the package remotely.

E.g. you can create an Agent job (without schedule) that
executes on serverA and then run it on demand from serverB.

Thanks,
Michael.|||Thanks for the confirmation Michael.|||

I have done as you suggested here and created an Agent job ... How do I call for the job in my vb code in the application? (Both SSIS & Application are on the same server)

Wes

|||

Wes Linz wrote:

I have done as you suggested here and created an Agent job ... How do I call for the job in my vb code in the application? (Both SSIS & Application are on the same server)

Wes

Use sp_start_job SQL stored procedure (see syntax in Books Online)

Execute Package Task behavior

I’m using a For Loop container to with an Execute Package Task inside, looping until a folder is empty.I’ve noticed some strange behaviors:

1. The child package keeps creating new connections.I start with 3 connections to the DB and when the For Loop container is done I’ve got 364 connections.

2. The Execute Package Task is pulling the wrong version of the package I’ve specified.I’m using a package saved to the File System and there’s only one copy on the drive.I’ve verified the path is going to the correct location.

Does anyone have a work-around for the ‘connection generation’ issue?

TIA

Eric

In your first question, do you load child packages from SQL Server? If yes - make sure you have connection pooling OFF.