I'm not an expert in this area but my gut feel is that the box isn't really the issue.
If you've already decided on XP Pro then get as much memory as it can address (which sounds like 3GB or 4GB from other posts). The speed of the network is going to be the bottle neck so can you modify the way the data is accessed? For example, I have seen huge differences between using SQL over ODBC and over OLEDB. If it is possible, use a technology like OLEDB that puts the processing as close as possible to the data to eliminate the network overhead. This is somewhat like using a stored procedure but it sounds like changing the configuration of the SQL boxes is not an option. What I am trying to say is that a slight change to the architecture may make all the difference. But I'm sure you know all that! Regards, Rob Wills (rob dot wills at tigerinfotech dot com) [EMAIL PROTECTED] wrote on 12/03/2007 19:51:53: > All, > I need some opinions! I have a client who is willing to spend to put > up a nice sized box, but they only want to spend once. Here's what they > need to do: run a 4 user copy of Universe, holding a Type 30 file with a > mere 200k records. Requests will range from give me one record (average > size is under 200 bytes) to give me all records. > The catch is that two SQL databases, with criminally slow network > connections will be feeding a fresh set of records every hour. > I need a recommendation on how much RAM and Processor to throw at > the system so that SQL joins (6 levels deep) don't slow down the > UniVerse part of the system. The response time has to be obscenely quick > (eCommerce for a very, very busy site). > All thoughts appreciated. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
