Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Run/Execute SSIS package before deploying it Expand / Collapse
Author
Message
Posted Monday, August 18, 2014 3:46 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, September 6, 2014 8:47 AM
Points: 8, Visits: 67
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.
Post #1604703
Posted Tuesday, August 19, 2014 12:36 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 8:29 AM
Points: 12,945, Visits: 10,716
You hit F5 in BIDS.



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1604762
Posted Tuesday, August 19, 2014 1:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, September 6, 2014 8:47 AM
Points: 8, Visits: 67
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?

Post #1604772
Posted Tuesday, August 19, 2014 1:47 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 8:29 AM
Points: 12,945, Visits: 10,716
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.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1604773
Posted Tuesday, August 19, 2014 6:50 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, September 6, 2014 8:47 AM
Points: 8, Visits: 67
So, only debugging we can do when the package is not deployed.
thanks.
Post #1604879
Posted Tuesday, August 19, 2014 6:08 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 6:01 PM
Points: 356, Visits: 871
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.
Post #1605254
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse