Select the database used by the WSUS Server

The WSUS Server database stores the following information:

WSUS server configuration information;

Metadata used to describe the role of the update program;

Client Computer, update program information, and updates made by client computer.

You cannot directly access the database to manage WSUS. You must manage WSUS through the WSUS console. Each WSUS server needs its own database. If it has multiple WSUS servers, it must have multiple WSUS databases. WSUS does not support placing multiple WSUS data inventories on a single computer running SQL Server, because WSUS can only use a database name named SUSDB.

You can use a database that is fully compatible with Microsoft SQL as a WSUS database. However, we recommend that you use one of the following three types:

The Microsoft Windows SQL Server 2000 Desktop Engine WMSDE that is attached to WSUS only exists on the WSUS server installed on Windows Server 2003, WMSDE is installed by default when WSUS is installed on Windows server 2003. The difference between it and the following MSDE is that there is no database size limit, and WMSDE and MSDE do not come with administrative tools or user interfaces. If you are reluctant to use Microsoft SQL server when installing Windows Server 2003, we recommend that you use WMSDE. We recommend that you always deploy the WSUS service on Windows server 2003 and always use the WMSDE database.

Microsoft SQL Server 2000 Desktop Engine MSDE), which can be downloaded from Microsoft for free. It is based on SQL Server 2000, but the database size cannot exceed 2 GB. You can use MSDE to install WSUS on a computer running Windows 2000. If you are reluctant to use Microsoft SQL Server when installing it on Windows 2000, MSDE is recommended.

For Microsoft SQL Server 2000 with SP3a Patch, you must enable the SQL Server nested trigger option before installing WSUS. The database recursive trigger option is enabled during WSUS installation, but the global nested trigger option of the server is not modified.

WSUS supports SQL databases on other computers, but has the following restrictions:

Windows 2000 Server cannot be used as the front-end server for remote SQL;

The server configured as the domain controller cannot be used as the front-end or back-end server of the remote SQL pair;

You cannot use WMSDE or MSDE as the database software on the backend server.

WSUS only supports Windows Authentication regardless of the database type. When WSUS is installed, the drive that stores the WSUS database must have at least 2 GB of free space.

Determine the storage location

An Update is an alternative to a patch or entire file of software installed on a computer. Each available Update on Microsoft Update consists of the following two parts:

Metadata that provides updated information, such as property information about the update program, so that you can understand the usefulness of the update. In addition, metadata also includes the End User License Agreement EULA ). The downloaded update metadata package is usually far smaller than the actual Update file package.

An Update file is the actual file required to install updates on a computer.

When you synchronize updates to the WSUS server, the metadata and update files are stored in two different locations. Metadata is stored in the WSUS database. The updated files can be stored on the WSUS server or Microsoft Update Server Based on the synchronization configuration options.

1. Local Storage

You can store the Update file on the WSUS server, which saves the bandwidth of the external network connection of the enterprise, because the client computer directly obtains updates from the WSUS server, which is also the default option. For local storage, the WSUS server requires at least 6 GB of space to store the updated files during installation. We recommend that you use 30 GB space. However, depending on the product and category synchronization options, the Update file may exceed 30 GB.

2. Remote Storage

If you need it, you can save it locally. In this case, the Update file is stored remotely on Microsoft Update. When the WSUS server is synchronized with Microsoft Update, only metadata is downloaded. You can approve the Update through the WSUS console. During installation, the client computer directly obtains the Update file from Microsoft Update. As shown in the Update process, this provides better results for client computers to access Microsoft Update faster than WSUS.