Hi,
myDBR itself scales easily to large number of user (including public web portals). There is no performance effect with number of reports created.
myDBR uses databases stored procedures in database directly meaning the performance is pretty much as good as it can be with given hardware and sw-stack. This applies to all supported databases (MySQL, SQL Server, Sybase). Also the way myDBR uses the database (single connection with processing done on database server closest to data) provides the optimal performance.
Apache has traditionally been performing better with PHP, but with latest work done with PHP running on Windows has closed the gap. Selection of web server can really be done based on which your organization feels most comfortable with.
MySQL and SQL Server have bit different characteristics. Generally speaking SQL Server offers solid query optimization, but MySQL with it's cluster offering (and price) has advantages with in-memory databases in very large scale installations.
If you do expect high amount of traffic for myDBR installation, concentrate optimizing the queries inside the reports. Query optimization is the biggest part of the performance. Poorly optimized heavy queries take long time to complete and take lot of resources, compared to well optimized SQL code. With using stored procedures, myDBR reports are easy to optimize. You have all database optimization means available, compared to traditional reporting systems where database access is often divided into multiple separate serialized queries, with no means of optimizing the data access between the objects in report.
--
myDBR Team
