Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
PeterParker
Starting Member
3 Posts |
 Posted - 2009-12-08 : 07:26:07
|
| Hello,For a client I need a to write a rapport to persuade them to get a special integration server. Right now it runs on the same server as the database. Has anybody encountered problems with this that I could use in the rapport or any other fundamental drawbacks of running on the same server?TIY,PP |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-12-08 : 12:50:19
|
| Do you mean a dedicated job server?Probably a good idea. Depends on how much overhead the jobs themselves cause. Also on network speed.We use dedicated job servers -- mostly to consolidate all of our jobs to one (ok a few) place.How many production servers do you have? If just one, I wouldn't bother with a 2nd server just to run SQL Agent jobs.Another consideration is SQL licenses. You're going to have to convince someone that it's worth several thousand dollars to add a SQL Server simply to run jobs.Also, need to consider edition, and server specs. You'll need a much less robust server if all it does is run jobs |
 |
|
|
PeterParker
Starting Member
3 Posts |
Posted - 2009-12-14 : 10:01:16
|
| Thanx. Yes that is what I meant. A dedicated job server. I also need some examples of what could go wrong with one server for rdbms and ssis. They only have one production server but apparently that is running tired from the extra load. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-12-14 : 11:04:10
|
| it is probably the load of what the jobs are doing, and not the jobs themselves.moving the jobs to another server isn't going to help performance-wise if they interact with data on the production server |
|
|
|
|
|
|
Integration service and database on same server