SSIS packages - project vs package, how to save, basics

Hi guys,

What is the difference between an SSIS solution, a project, and a package? Can I save a package file outside of the default folder structure for SSIS? If I do, does the project/solution information come with it? Can I name my project with a special name? It looks like it always says "Package.dtsx", can I change that?
JC_LivesAsked:
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.

Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
Yes, you can change the package name whatever you would like. that basically is goes with your work is related to.

What is the difference between an SSIS solution, a project, and a package?
if you want to have configuration at project project level e,g, global variable for all package in that project you should consider to use as project level parameter which you can configured using environment variable.


you can provide file server location where package stored or SSISDB location.

you can deploy the complete solution which might have multiple package and get deployed under the same solution. (it will ask to create a folder in which the solution will deploy) .
Rainer JeschorCommented:
Hi,
a SSIS solution is nothing special to SSIS - its just a container for Visual Studio projects - hence you can have e.g. the SSIS, the SSAS, the SQL database and the SSRS projects inside the same solution.
A SSIS project is a collection of packages and can have project related parameters (new in SQL Server 2012). There is no folder structure in a SSIS project hence all packages are/have to be on the same level.
When you create a SSIS project you can set the deployment model to either project or package deployment model. A project can be deployed only as one complete entity (all packages inside the project), which might cause issues if you have a distributed team working on multiple change requests in parallel and having no agreed complete (tested, documented, approved, UATed) project "version". You might think about using branching and merging strategies but that will become complicated very quickly.
Packages can be deployed either on the file system, into the MSDB or SSIS catalog store (since SQL 2012).
One limitation e.g. of the "Execute child package task" is, that it can only execute packages in the same project.
You cannot save packages outside the projects folder in regards to development, but using different folder(s) for deployment (file deployment in package deployment model).
SSIS is a really huge area, so if you have to get into SSIS, there are a couple of really good books from Wrox and Apress covering 95% of the topics - the rest is experience.
Just my 2ct (or better 20ct) ;-)
Rainer

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
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.