Solved

SSIS Packages Configurations and Deployment

Posted on 2011-02-11
3
401 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 500 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

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

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

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This post contains step-by-step instructions for setting up alerting in Percona Monitoring and Management (PMM) using Grafana.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…

724 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