>Sorry for the confusion...the table we are querying contains 600,000+ records. We are only bringing back a single customers records which averages around 50 records.

Well, this is absolutely better. 8-)

Now, how many simultaneous accesses like this you foresee. Take in consideration that by simultaneous, I mean *actually* performing the query at the same time. That doesn't count a user who is just reading information from the web page (what happens most of the time).

Also, how much the average query takes to resolve in a single instance of the component?

See you,