Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Ideal SSIS Package deployment Expand / Collapse
Author
Message
Posted Tuesday, August 27, 2013 1:50 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 9:12 AM
Points: 14,608, Visits: 12,669
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?

Member of LinkedIn. My blog at SQLKover.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1488593
Posted Tuesday, August 27, 2013 1:53 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Friday, July 24, 2015 8:43 AM
Points: 3,600, Visits: 2,723
Both in 2008. I deployed them to file system. (Not the default path but to new folder with the project name )
Post #1488596
Posted Tuesday, August 27, 2013 2:00 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 9:12 AM
Points: 14,608, Visits: 12,669
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?

Member of LinkedIn. My blog at SQLKover.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1488600
Posted Tuesday, August 27, 2013 2:13 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Friday, July 24, 2015 8:43 AM
Points: 3,600, Visits: 2,723
Thanks for the second answer Koen. Thanks cool. On first one, let me check once again today and get back by tomorrow.
Post #1488604
Posted Sunday, July 19, 2015 12:30 AM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Sunday, July 19, 2015 12:31 AM
Points: 33, 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.
Post #1704081
Posted Monday, July 20, 2015 1:47 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 9:12 AM
Points: 14,608, Visits: 12,669
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?

Member of LinkedIn. My blog at SQLKover.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1704149
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse