?
Solved

SSIS Packages Configurations and Deployment

Posted on 2011-02-11
3
Medium Priority
?
403 Views
Last Modified: 2012-05-11
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
Comment
Question by:Lyn Udy
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 5

Accepted Solution

by:
robertg34 earned 2000 total points
ID: 34873207
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
 

Author Comment

by:Lyn Udy
ID: 34873276
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
 
LVL 5

Expert Comment

by:robertg34
ID: 34875139
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

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this series, we will discuss common questions received as a database Solutions Engineer at Percona. In this role, we speak with a wide array of MySQL and MongoDB users responsible for both extremely large and complex environments to smaller singl…
Your data is at risk. Probably more today that at any other time in history. There are simply more people with more access to the Web with bad intentions.
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question