Mike
There are two applications here on batch application to get data into the database and the other for reporting.
Regarding the batch mode one – you can consider using SQL Server's Integration Services (SSIS – formerly ETL).
Regarding the number of users are you talking about 300 concurrent users or a total of 300 users - if you really expect 300 users hitting the DB simultaneously I doubt that a single server would suffice. Since (as you describe it) the data is mostly read-only (with daily batch-updates) it shouldn't be too much of a problem to have multiple copies of it and scale the solution. Also if you only query the data you may consider exposing the queries as web-services directly from the database (again this is assuming you don't have any real business logic)
Arnon
|