x

SSIS Connection Manager / Config Theory

Two weeks ago I did a rebuild and deploy via the manifest a new version of my SSIS 2005 project. During the publish using the manifest, I changed the connection managers in the manifest to hit my production server. I also use an XML package config file on the production server that is stored in a separate location and is never overwritten.

Do I need to change the connection data in the manfest tool? I ask this because I think I don't, but I do it to be safe.

For some reason, this rebuild did not point to the production environment but test, so 2 weeks of data went to the wrong place. Since I use the xml config file in every package of the project what could have happened that the connections were incorrect? Any thoughts, ideas or suggestions regarding the process would be very helpful.

Thanks!
more ▼

asked Nov 20 '12 at 07:41 PM in Default

paws27284 gravatar image

paws27284
353 22 28 32

(comments are locked)
10|1200 characters needed characters left

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x1933
x898

asked: Nov 20 '12 at 07:41 PM

Seen: 443 times

Last Updated: Nov 20 '12 at 07:41 PM