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 |
|
bluedolphin
Starting Member
24 Posts |
 Posted - 2006-09-13 : 11:48:43
|
| Hello All:I learned today that the boss is considering buying us a new and bigger SQL server box. One of my collegues has noticed that the box server is using 95% CPU when we are running aggregations as well as serving reports from reporting services.We currently have both SQL Server and Reporting Services installed on the same box. The discussion so far has been to beef up the one box that is hosting both services to a 4X. I lean towards thinking that we should seperate Reporting Services onto its own box, giving SQL its own dedicated environment. We are not sure which model will give us the best performance boost.Anybody have prior experience with this and knows the better scenario to go with? Thanks BC-T |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-09-13 : 12:37:36
|
| Yes Reporting Services should be separated to its own box. In fact, that's the recommendation since RS uses IIS. IIS and SQL Server should not be on the same box for more environments. When you do use this architecture though, it does require an additional SQL Server license for RS. We are currently running this type of architecture in our production environment. RS is on our web server that hosts our web applications. They live together just fine. IIS and SQL Server do not live together fine due to memory utilization.Tara Kizer |
 |
|
|
|
|
|
Reporting Services on same box as SQL