locked
WSUS 3.0 - Requirementes of DB and Hardware RRS feed

  • Question

  • Hi,

    I need to install WSUS 3.0 on a Windows 2008 Server R2. In my environment I have about 250-300 computers. I wonder if the Windows Internal Database meets this environment, and how much memory and hard disk will be necessary for the proper performance of WSUS. I read that the WID (Windows Internal Database) has no limitations to WSUS, however, would like to know in relation to his performance in this environment. I also read that database SQL SERVER EXPRESS are not recommended because of its limitation. 

    Anyway, I would like to know your technical point of view. Thank you.


    Wednesday, August 6, 2014 12:47 PM

Answers

  • I wonder if the Windows Internal Database meets this environment, and how much memory and hard disk will be necessary for the proper performance of WSUS. I read that the WID (Windows Internal Database) has no limitations to WSUS

    I also read that database SQL SERVER EXPRESS are not recommended because of its limitation. 


    I don't normally refer people to legacy documentation, but this chart (which is still valid) from the WSUS3SP1 Deployment Guide was left out of the WSUS3SP2 documentation set. I believe it will answer almost all of your questions.

    Simply stated, WSUS requires very little resources to run, the majority of the requirements are to support the database engine. For a few hundred clients, a single-core hyperthreaded P4 x86 with 2GB RAM is quite sufficient, but given that you are deploying on WS2008R2, you should start with 4GB RAM.

    The Windows Internal Database is a fully functioning SQL Server database engine. It's only limitations are

    • it doesn't ship with client tools, but SSMS can be used to access the database
    • it's licensed for use only by Microsoft native applications

    SQL Server Express Edition IS limited in its capabilities. It's throttled to use only a single CPU and only 1GB RAM for buffering. As such, it is inappropriate for use in a WSUS Server. Additionally, versions prior to SQL2008R2 were also capped at 4GB per database, which is insufficient space for a WSUS server. There is *NO* reason to use SQL Server Express Edition as an alternative to the Windows Internal Database.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Monday, August 18, 2014 5:42 AM
    Wednesday, August 6, 2014 4:28 PM

All replies

  • Hi

    http://technet.microsoft.com/en-us/library/dd939928(v=ws.10).aspx

    Wednesday, August 6, 2014 2:31 PM
  • regarding the DB engine comparisons:

    http://technet.microsoft.com/de-de/library/dd939812(v=ws.10).aspx

    I've had WSUS with 500 clients running on WID and it was fine. of course things like reports and update approvals to multiple groups can take some time but it works and you save licensing costs for SQL

    system requirements are loosely outlined here:

    http://technet.microsoft.com/en-us/library/dd939928(v=ws.10).aspx

    it doesn't mention RAM but I think 4GB RAM is enough to start with for an environment of your size

    regarding disk space, it's tough to guess, it depends how many products you are updating, normally 50GB is a safe number

    Wednesday, August 6, 2014 2:42 PM
  • I wonder if the Windows Internal Database meets this environment, and how much memory and hard disk will be necessary for the proper performance of WSUS. I read that the WID (Windows Internal Database) has no limitations to WSUS

    I also read that database SQL SERVER EXPRESS are not recommended because of its limitation. 


    I don't normally refer people to legacy documentation, but this chart (which is still valid) from the WSUS3SP1 Deployment Guide was left out of the WSUS3SP2 documentation set. I believe it will answer almost all of your questions.

    Simply stated, WSUS requires very little resources to run, the majority of the requirements are to support the database engine. For a few hundred clients, a single-core hyperthreaded P4 x86 with 2GB RAM is quite sufficient, but given that you are deploying on WS2008R2, you should start with 4GB RAM.

    The Windows Internal Database is a fully functioning SQL Server database engine. It's only limitations are

    • it doesn't ship with client tools, but SSMS can be used to access the database
    • it's licensed for use only by Microsoft native applications

    SQL Server Express Edition IS limited in its capabilities. It's throttled to use only a single CPU and only 1GB RAM for buffering. As such, it is inappropriate for use in a WSUS Server. Additionally, versions prior to SQL2008R2 were also capped at 4GB per database, which is insufficient space for a WSUS server. There is *NO* reason to use SQL Server Express Edition as an alternative to the Windows Internal Database.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Monday, August 18, 2014 5:42 AM
    Wednesday, August 6, 2014 4:28 PM