svdl, good point about the stored procedures. I am positive Rosity doesn't make optimal use of them considering the SQL output on the homepage on a failed log in. There is a lot of dynamic SQL on the site. I would hope this would be changed in 3.0

BTW: There is a big difference between 1500 and 2k-plus users connecting to a DB at one time. You have to understand how DBs work, or you really don't get why Rosity is slow. MySQL is a great DB, but not for as large a scale as Rosity uses it. But then again, using an industrial-strength DB would be tough cost-wise to justify. With products like Oracle or SQL Server, you pay for things like number of processors running the software. It wouldn't be cheap. Unless you want Rosity to start recouping that money from us (either by charging vendors more for purchases, or charging membership) you may have to deal with a lower standard of performance.