Points to consider for Report Database.

Ok..ok, I'm trying to get some comment/ insight on what things to consider during developement of a
Reporting module with a Reporting Database. For those who had face problems, been doing something like this, maybe you like to share a tip or two.

Project:

Developing ASP/ ASP.NET applications through DNSless connection with either OLE or ADO drivers to a SQL Server Report Database. Users will login in the browser to view reports of their choice. Not using any OLAP cubes. It would simply be callling SPs and query the tables for data and displaying it in cuztomize HTML report formats. And of course with good indexing.

Project scope:

Enterprise/Factory scale -so to assume Reporting DB size easily over 50-70 GB.

QUESTIONS:

1. How many users can concurrently login to view reports? A rough estimate would be? Is there any unit of measurement to determine the number?

2. What are the best practices- in DB design and and on application development for this project case?

3. What are the hardware concerns/specs ( best/minimum recommendations)? Would network traffic play a role here?

Thanks in advance for sharing your comments.It depens on what kind of database is but anyway:

1. Quantity of users depends on database and application design (respond time, etc.)
2. Best way - to create datawarehouse
- denormalize tables (less joins)
- a lot of indexes
- access only by sp
- you could create a fake cubes (I did it - it works even better than MS cubes for my case)

3. Ask for more and get something better... ;)sql

Please Provide INSIGHT - why Winforms or WebParts with RS?

I would appreciate some clairvoyance on this subject:
Why is it necessary to use WINFORMS or WEBPARTS to execute a Reporting Services Report? My naive understanding is that RS is an enterprise reporting tool...
If I want to develop an OLTP application I use something different and if I need to print (via RS) I provide a button that goes to a "un" hyperlink that then provides me the rich functionality of RS.....
So it seems for sure I am missing something here - please and sinncerely give me some insight!
Best reagrds,
Joe

Sorry for the delayed posting, hopefully it can still be useful.

I'm notentirelysure I understand your post so bear with me;
In fact you don't need to use WinForms nor WebParts, you can simply provide the user a url that directly points to the report or let's say an Excel output...

Sample url for Excel output:
http://<your server>/reportserver?/<your path>/<your report name>t&rs:Command=Render&rs:Format=XML&rc:Parameters=False&rc:XSLT=<your xslt file>.xslt&rc:MIMEType=application/vnd.ms-excel&rc:FileExtension=xls
Sample url for a Report output:
http://<your server>/Reportserver?/<your path>/<your report name>&rs:Command=Render
On the other hand you can create your own custom interface to output the reports in the way you see fit, such as data-filled dropdowns or any other control. You can also have any of these controls interact with the report itself
Unfortunately that's a bit more involved and I will not detail it in this post, I may in the near future write an article on this.