• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 409
  • Last Modified:

SSIS Packages Configurations and Deployment

I have 12 packages in my SSIS project to configure and deploy; what are the major things to change in these two processes to ensure smooth package preservation? Is it ok to select all properties in the 'Select Properties to Export' page?

I had configured and deployed a trial copy package and after that I tried running the package again but it failed; should that be expected? What If I want to run the package in future, is there anything I need to turn on or off on the configuration properties?

When I schedule sql server job, would this failure affect the  job from executing?
Thanks
0
Lyn Udy
Asked:
Lyn Udy
  • 2
1 Solution
 
robertg34Commented:
Select the bare minimum you need in the configuration selection.  I try to stick with the connection string only.  When I deploy, I simply change the server names to point to the correct production servers in the xml file.  

If the job is failing when you run it manually, it will most likely fail when you run it as a scheduled job.  

This video may be of some assistance to you:
http://www.sqlshare.com/OptionsforDisplayingQueryResultsinSSMS_853.aspx
0
 
Lyn UdyDonor Database AdministratorAuthor Commented:
I am using SQL Server method for the configuration and deployment. Can the connection manager be changed as well using this method?

What can I do then to make sure that the package doesn't fail when I run it either manually or as a scheduled job? But just before the configuration and deployment, the package was running very well with no error so I'm wondering if there's anything that could be done during the configuration or deployment to prevent the package from not running. By the way, the error is primary key constraint.

Thanks!
0
 
robertg34Commented:
The connection manager can be changed using the configuration using either sql server or the .xml file.  

With a primary key constraint failure, it sounds like you need to add a sql task to your package that disables the constraints before the data is loaded.  At the end of the job you can another sql task that re-enable the constraints.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now