Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 2109 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sizing Enterprise Console

mbro

Hi There,

Just looking for a bit of advice. We will need to build a server to support 1000 Windows endpoints. Are there any guides available to help size this server? Would it require a SQL database rather than SQL Express?

Thanks

:6525


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    SQL Express will be fine for that size installation, the main things to think about are disk I/O and memory.  SQL will consume both but mainly I/O and the RouterNT.exe process will consume quite a bit of memory for that number of clients, I would imagine somewhere in the order of 200-250MB.  SUM will also consume quite a bit of disk I/O when updating.

    I would advise if starting from scratch you might want a dedicated physical drive to store the databases on. In an ideal world separate drives for SQL data (mdf) and logs (ldf) but for this size installation a dedicated drive for SQL express "data" will be better than putting it all on the OS drive.  

    I would suggest 4GB of RAM as a minimum and either Win 2k3R2 or 2K9R2 as the OS.  SQL Express 2K8 SP1 will be installed by default.   SQL 2008 R2 is not currently supported until 4.7 I think.

    If you find that the server you have in mind is not powerful enough, things you can consider to lighten the load off one machine are:

    1. Write the CIDs/Distribution points to a file server/filer, so the clients update from there.

    2. Remove/Move other roles to different servers.

    3. Move the database to a remote machine, can still be SQL Express.

    As these can all be done at any time, you can monitor the resources used and make these decisions later.

    Here are a couple of other posts I've made along these lines:

    Jak

    :6527
Reply
  • 0

    Hi,

    SQL Express will be fine for that size installation, the main things to think about are disk I/O and memory.  SQL will consume both but mainly I/O and the RouterNT.exe process will consume quite a bit of memory for that number of clients, I would imagine somewhere in the order of 200-250MB.  SUM will also consume quite a bit of disk I/O when updating.

    I would advise if starting from scratch you might want a dedicated physical drive to store the databases on. In an ideal world separate drives for SQL data (mdf) and logs (ldf) but for this size installation a dedicated drive for SQL express "data" will be better than putting it all on the OS drive.  

    I would suggest 4GB of RAM as a minimum and either Win 2k3R2 or 2K9R2 as the OS.  SQL Express 2K8 SP1 will be installed by default.   SQL 2008 R2 is not currently supported until 4.7 I think.

    If you find that the server you have in mind is not powerful enough, things you can consider to lighten the load off one machine are:

    1. Write the CIDs/Distribution points to a file server/filer, so the clients update from there.

    2. Remove/Move other roles to different servers.

    3. Move the database to a remote machine, can still be SQL Express.

    As these can all be done at any time, you can monitor the resources used and make these decisions later.

    Here are a couple of other posts I've made along these lines:

    Jak

    :6527
Children
No Data