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

Where is the ideal place to install SSIS? Expand / Collapse
Author
Message
Posted Friday, May 10, 2013 8:12 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 12:24 PM
Points: 130, Visits: 384
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
Post #1451614
Posted Friday, May 10, 2013 4:14 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 8:08 AM
Points: 35,366, Visits: 31,906
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1451773
Posted Saturday, May 11, 2013 7:37 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 12:24 PM
Points: 130, Visits: 384
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!
Post #1451828
Posted Saturday, May 11, 2013 12:35 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 8:08 AM
Points: 35,366, Visits: 31,906
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1451849
Posted Tuesday, May 14, 2013 3:59 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:42 AM
Points: 13,295, Visits: 11,086
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 LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1452474
Posted Thursday, June 6, 2013 4:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, September 25, 2014 11:05 PM
Points: 338, Visits: 463
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.


Joe
Post #1460605
Posted Tuesday, June 11, 2013 10:05 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 8:46 AM
Points: 40, Visits: 478
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
Post #1462258
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse