Run/Execute SSIS package before deploying it

Question

Run/Execute SSIS package before deploying it

previn1980

Old Hand

Points: 379
More actions
August 18, 2014 at 3:46 pm

#292469

Hi to all
i'm a newbie of SSIS. I started to work with ssis packages few months ago as analyst and I haven't yet started to developing SSIS packages.
What I'm wondering from a couple of days is: how to we run/execute a SSIS package during the development phase before the package deploy on the SQL Server??
Suppose that I'm on the client machine and I'm developing with BIDS in offline mode and I want run/execute the package for each new Task that adding to the package for testing purpose.
How to do this if we have not yet the deploy of the package on the SQL Server instance/engine?
thanks.

Viewing 6 posts - 1 through 5 (of 5 total)

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

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 1

You hit F5 in BIDS.

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

previn1980 Old Hand Points: 379 More actions · Answer 2

f5 starts the debugging process.

A package for to be debugged it need of to be in execute. is it right?

But how to works the debugging process without deploying on the SQL Server?

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

You debug the package in Visual Studio.

When debugging, the package will run locally inside BIDS.

If you want to run the package outside BIDS but not on the server, you need a machine where Integration Services has been installed. Then you can run the package through the command line with DTEXEC.

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

previn1980 Old Hand Points: 379 More actions · Answer 4

So, only debugging we can do when the package is not deployed.

thanks.

MMartin1 One Orange Chip Points: 27799 More actions · Answer 5

If you are concerned about how it will run in a job, you can deploy it to a test machine with the job service running under the same credentials ...security context as the one on the production system. See if you can access the needed outside resources that way. Though that would depend on your situation if this is even possible.

Note: Some systems cannot run the DTEXEC because the command shell is not on due to security. Here you can simply define the job step as a integration services package.

----------------------------------------------------