SQL 2000 Reporting Services Architecture

[Moses]

I am in the initial stages of setting up a Reporting Services on a production
envronment and I am not sure how to go about setting this up. I currently
have 2 web servers and 2 sql servers. I also have an aditional server that
could be used if needed. My initial thought was to instal sql and reporting
services on both web servers but there could be some possilbe issues. Then I
was thinking about putting sql and reporting services on our extra server.
Does any one have any real life experience setting this architecture that can
pass along some best practices?

I would appreciate any feedback I can get.

Thanks,

Moses

[Arnie Rowland]

Reporting is CPU, Memory, and I/O intensive.

I prefer to have a separate Reporting Server when possible. Then either set
up replication or log shipping to move the production data to the reporting
server. If you have extensive reporting needs, you may find that more CPU
and Memory resources are needed.

I wouldn't recommend installing Reporting Servers on the Webservers.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf

"Moses" <Mo...@discussions.microsoft.com> wrote in message
news:4A42855A-79F1-47CF...@microsoft.com...

[Moses]

Thanks for the response Arnie,

I've done some research and I can't find any one who has an actual set up
using reporting services. We currently have 2 web servers load balanced and
an additional server to handle reporting services. I guess this is the best
set up we could come up with. Is any one else running into this set up issue?