468,113 Members | 2,149 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,113 developers. It's quick & easy.

Best Practises for Server Sizing for MS Reporting Services

We are planning to deploy the MS Reporting Services. Unfortunately,
there isn't much guidance on how to effectively size a server.

Here are my questions:

1) In an environment with 1 reporting server (hosting the reporting
data layer, application, and management layer) connecting to 1 or more
SQL servers (over 2 trunked 1Gbps switches connections), what is the
constraining resource when running large reports against a database of
say 4GB in size? CPU, RAM, DISK, or Network speed on the Reporting
Server? Or the Data hosting SQL server? Or does it depend on code?
2) If I have a Duel Core CPU, do I buy 1 CPU license. MS had responded
to the HyperThreading as 2 virtual CPUs with the statement that you buy
CPU licenses based on socket count effectively. This would imply that
if I buy a 4 Duel Core AMD Opteron Proliant 585 (8 CPU cores in 4
packages / sockets), I can run MS Reporting Services Standard Edition.
Is that true?

Any input or direction would be appreciated.

Paul V.

Jul 23 '05 #1
1 3304
You might want to post in microsoft.public.sqlserver.reportingsvcs to
see if you get a better response.

For licensing issues, there is an FAQ, but if it doesn't answer your
question it would probably be best to contact Microsoft directly for a
definite answer:



Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Paul Say | last post: by
8 posts views Thread by Woody Splawn | last post: by
1 post views Thread by yhafeez1 | last post: by
3 posts views Thread by =?Utf-8?B?Sm9uIEphY29icw==?= | last post: by
reply views Thread by TOM GUGGER | last post: by
3 posts views Thread by didacticone | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.