Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Where is the ideal place to install SSIS?


Where is the ideal place to install SSIS?

Author
Message
Crosan
Crosan
SSC-Enthusiastic
SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)

Group: General Forum Members
Points: 130 Visits: 403
We're currently working on building out a new data warehouse and I'm looking for resources or best practices on where SSIS is should ideally be installed. My thoughts are as follows, but I'm really looking for a best practices document or other documentation that outlines any other architectural gotcha's for this setup.

1. On the same server as the data warehouse database

Pros:

No additional licensing cost
Lower network latency, since it just needs to pull from the sources
Lower hardware costs

Cons:

Will contend with or lower the amount of memory SQL Server has at it's disposal for proc and buffer cache (this is big deal my this case)
Will contend with CPU (CPU is typically very low on this server, so not such a big deal)

2. On a separate stand alone server

Pros:

SSIS won't contend for resources with the database the DW server

Cons:

Higher Network latency
Higher hardware costs
Higher licensing costs
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44896 Visits: 39857
I'm a bit confused. When speaking of a data warehouse, don't you mean SSAS?

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
     Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Crosan
Crosan
SSC-Enthusiastic
SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)SSC-Enthusiastic (130 reputation)

Group: General Forum Members
Points: 130 Visits: 403
Jeff, thanks for the reply. We're planning to use SSIS to ETL the data, I'm just not sure I've seen any recommendations on where it should be installed. In the past I've run it on the same box the Datawarehouse runs on, but that's just because it seemed the most logical place to put it. And would there be any benefits other than the ones I listed to having it installed on it's own server or elsewhere? Thanks!
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44896 Visits: 39857
Ah. Got it. Agreed. If it were me, I'd put SSIS on the same box as a data warehouse just for the extra kick in speed. There's nothing like being close to the work. Of course, if it's a shared SAN that the DW is on, that might not matter. The other advantage might be in the cost of licensing.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
     Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Koen Verbeeck
Koen Verbeeck
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16366 Visits: 13199
If you design your packages right - in the sense they do not use too much memory - you can put SSIS on the same server.
Avoid blocking components (such as the SORT component) and asynchronous components.

If you use a lot of SQL in your packages, there's no reason for not putting it on the same server. Most of the work will be done by the database engine anyway.



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
dfine
dfine
SSChasing Mays
SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)SSChasing Mays (621 reputation)

Group: General Forum Members
Points: 621 Visits: 597
I would recommend you to consider these points to decide where to host your package.

Are you going to run the package in any specific time let’s say once in a day (nightly job)?
How often users / applications connects to the DWH DB?
How many jobs are running parallely?

but still I believe hosting the package on the same machine will be better than another server. If you think performance is an issue, you have options to upgrade your hardware than going for new machine.

Raj
peterjonk
peterjonk
SSC Rookie
SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)SSC Rookie (41 reputation)

Group: General Forum Members
Points: 41 Visits: 611
Well I am also investigating the pros and cons of placing SSIS on the DB server.
http://www.sqlservercentral.com/Forums/Topic1459119-391-1.aspx#bm1459772

I think most of the pro's of putting SSIS on the DB server have been mentioned.
- Less licensing costs
- Performance benefits: the packages run close to the data (less network traffic)
- Easier scheduling via SQL agent is also a pro.

Cons
- SSIS packages compete for resources with DB engine (however most load occurs on the DB server anyway)
- Some SSIS packages won't run correctly if DB server is not in a DMZ

The last one is a problem for us because some packages access external sites (like FTP).
I think I can workaround this to implement some generic FTP service running on a seperate application server in DMZ to download the FTP files and put it on the internal network.

__________________
MS-SQL / SSIS / SSRS junkie
Visit my blog at dba60k.net
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