WSUS 3.0 SQL 2005 Embedded Edition Limitations? johnf 5/15/2007 6:46:00 PM As I have run WSUS 2.0 using WMSDE and understood there were some limitations running WMSDE as opposed to the full blown MS SQL Server 2000. Can anyone explain what the limitations are running SQL 2005 Embedded Edition? Is it similar to that of WMSDE? Thanks

RE: WSUS 3.0 SQL 2005 Embedded Edition Limitations? eddieb[ at ]online.microsoft.com (Eddie Bowers [MSFT]) 5/15/2007 10:45:13 PM It's the same limitations. The biggest one being that it has to run local to the WSUS server itself (no backend database on another machine). It doens't have the 2Gig database limit that plain MSDE had. Eddie Bowers Security Support Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights.

RE: WSUS 3.0 SQL 2005 Embedded Edition Limitations? Todd Murray 5/16/2007 3:45:01 PM "Eddie Bowers [MSFT]" wrote: [Quoted Text] > It's the same limitations. The biggest one being that it has to run local > to the WSUS server itself (no backend database on another machine). > It doens't have the 2Gig database limit that plain MSDE had. > > Eddie Bowers > Security Support > Microsoft Corporation > > This posting is provided "AS IS" with no warranties, and confers no rights. > > Is there a reccomended client maximum for the embedded DB?

Re: WSUS 3.0 SQL 2005 Embedded Edition Limitations? "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/21/2007 12:39:24 AM "Todd Murray" <ToddMurray[ at ]discussions.microsoft.com> wrote in message news:E2E13AB9-C477-48E2-B6C2-7FB9A8B9B94C[ at ]microsoft.com... [Quoted Text] > Is there a reccomended client maximum for the embedded DB? Not formally, Todd. the embedded edition, as with WMSDE on WSUS 2.0, has no limitations on its capability. In reality, however, it was found that WMSDE for WSUS 2.0 hit a performance ceiling (not because of the database, per se, but because everything was running on one system) at around 3,000 clients. Allowing for the performance enhancements of moving from WSUS 2.0 to WSUS 3.0, I'd be surprised if anybody was successful at supporting more than 4,500 clients in a single server deployment -- even with multi-core servers. The real bottleneck in loads that high will not be CPU/RAM, but will be disk i/o and network i/o -- both of which can be solved much cheaper by deploying a *second* WSUS server, than can be solved by enhancing disk subsystems or adding additional network bandwidth. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....