SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Ideal SSIS Package deployment


Ideal SSIS Package deployment

Author
Message
Koen Verbeeck
Koen Verbeeck
SSC Guru
SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)

Group: General Forum Members
Points: 61521 Visits: 13297
Where did you deploy them to? Which version of SSIS are you using?


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
sqlnaive
sqlnaive
SSCertifiable
SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)

Group: General Forum Members
Points: 6347 Visits: 2774
Both in 2008. I deployed them to file system. (Not the default path but to new folder with the project name )
Koen Verbeeck
Koen Verbeeck
SSC Guru
SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)

Group: General Forum Members
Points: 61521 Visits: 13297
If you deployed them to the filesystem, you can see them by going to that directory.
If you deploy to the filesystem (and not in MSDB or the SSIS package folder), you don't need to use the deployment wizard.
As they're just files, you can copy them from one directory to another.

If you only want to change a few packages, just copy those new packages to the server.


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
sqlnaive
sqlnaive
SSCertifiable
SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)SSCertifiable (6.3K reputation)

Group: General Forum Members
Points: 6347 Visits: 2774
Thanks for the second answer Koen. Thanks cool. On first one, let me check once again today and get back by tomorrow. :-)
Avijeet
Avijeet
SSC Journeyman
SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)SSC Journeyman (89 reputation)

Group: General Forum Members
Points: 89 Visits: 156
sqlnaive (8/22/2013)
Hello SSIS Masters, I'm currently going through the learning phase. I have two questions regarding package deployments:

Q1. What is the ideal mechanism to deploye the packages (and which one is GENERALLY fllowed across organizations) :
a. By using deployment utility
b. From within BIDS or Management Studio
c. From a command line using dtutil or xcopy

Q2. Where should you ideally place the your packages (and where are these GENERALLY stored across organizations):
a. in msdb database in SQL Server instance
b. in SQL Server instance
b. in file system

The question might seem foolish but i'm new and any clarification will help.




In my opinion, this decision would be driven by kind of environment you are supporting and number of ssis package you have to support.

You can loosely say, SSIS is not instance aware.
In case you are having Huge Boxes with multiple SQL Server instances created on them, then msdb would not be a good choice as SSIS packages for all instance would be saved under one msdb.

For instance : you have 4 SQL instances being hosted on a box and you choose msdb as a storeage area for your packages. In this scenario, SSIS packages belonging to all instances would be hosted in msdb of one instance only, you can chose this instance by updating .xml file.

So , in this scenario it would be better to store ssis packages as file shares.
Koen Verbeeck
Koen Verbeeck
SSC Guru
SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)SSC Guru (61K reputation)

Group: General Forum Members
Points: 61521 Visits: 13297
Avijeet (7/19/2015)
sqlnaive (8/22/2013)
Hello SSIS Masters, I'm currently going through the learning phase. I have two questions regarding package deployments:

Q1. What is the ideal mechanism to deploye the packages (and which one is GENERALLY fllowed across organizations) :
a. By using deployment utility
b. From within BIDS or Management Studio
c. From a command line using dtutil or xcopy

Q2. Where should you ideally place the your packages (and where are these GENERALLY stored across organizations):
a. in msdb database in SQL Server instance
b. in SQL Server instance
b. in file system

The question might seem foolish but i'm new and any clarification will help.


In my opinion, this decision would be driven by kind of environment you are supporting and number of ssis package you have to support.

You can loosely say, SSIS is not instance aware.
In case you are having Huge Boxes with multiple SQL Server instances created on them, then msdb would not be a good choice as SSIS packages for all instance would be saved under one msdb.

For instance : you have 4 SQL instances being hosted on a box and you choose msdb as a storeage area for your packages. In this scenario, SSIS packages belonging to all instances would be hosted in msdb of one instance only, you can chose this instance by updating .xml file.

So , in this scenario it would be better to store ssis packages as file shares.


Or just use the project deployment model and the SSIS catalog.


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search