>Too bad it isn't a real client-server app. Performance like that is absolutely inexcusable. I build systems where 2.5GIG is more likely a reference table than a major data table but since they are client-server systems, database processing is done on the server and essentially the client only gets the data needed to present to the display.
>
>Ask the SAP when they plan to convert to a client-server system.

I don't think it'll go true client-server any time soon. I'd be happy if they just increased their query timeout to some longer, or even user-defined value. That's got to be preferable to just having the client fall over like it does now (.Net unhandled exceptions, no less).

If you're building large systems, can you give us any idea of typical hardware a server would use, especially disk subsystem(s)? I realize you're talking true client-server so it may not be directly comparable, but it would still be a useful data point.