SSIS PACKAGES

Hi

I have a development warehouse database and staging database refered to as db1. The databases is loaded with SSIS PACKAGES refered to as ssis 1.

I have created another warehouse database and staging database of the same schema refered to as db2. I did not want to re write the packages ssis1 so i coped them from the project folder and pasted them in a new folder. i then created a new projected  ssis2 and added the existing packages using the wizard. The problem i am having is when i amend the connections in ssis2 to point database db2 it updates the original packages (ssis 1) as well as ssis2!

is this a bug in ssis or am i doing something wrong, what is the correct way of repointing the connections?
ac_davis2002Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ValentinoVBI ConsultantCommented:
You've probably forgotten to update one or two connection managers.  The best method to ensure your connections are going to the right database is by using Package Configuration.  Using that method will centralize your configuration items, such as connection strings, and will make it easier to use the same packages on several different environments (DEV, INT, PRD).

Let's try to get you started.  There are five different types of configuration.  The ones you'll encounter most are XML Config file, SQL Server table and Environment variable.  Try experimenting a bit with this.  For instance, try configuring a test package using XML Config file to get a connection manager to point to another DB.  Use a simple Execute SQL statement to write something to a test table.  Then check your DB if the test record ended up in the right database.

More info:
http://msdn.microsoft.com/en-us/library/cc895212.aspx
http://msdn.microsoft.com/en-us/library/ms141682(v=sql.105).aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ac_davis2002Author Commented:
Thank you
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.