sql server reporting services: See comments inline.


[quoted text, click to view]

Install and set up reporting services on SQL Server is not too difficult.
However, since the Reporting Services is combination of ASP.NET web
application and Windows service and access to high secureable SQL Server,
you need understand user accounts that are used to run these services, in
order to choose correct one during installation.

[quoted text, click to view]

Autoring the reports and deploy them to reporting service server. Do author
report, you need VS2003 and install Reporting Services' client tool (report
designer, which is VS2003 add-in) on the developing box

[quoted text, click to view]

You do not need to access a real production data source to design report.
You do not need to connect to a rrunning reporting services either. However,
you do need a test data source (the database where report gets data from) to
develop report.

[quoted text, click to view]

Yes, SQL Server 2000 Developer Edition runs reporting services. (To run it,
you also need IIS running)

[quoted text, click to view]

I have a client that uses SQL Server 2000. They would like to automate some
reports, including saving them as PDF files. I'm considering the use of SQL
Server 2000 Reporting Services. Currently, their server that is hosting sql
server is only being used for the application.

My questions:
1. What all is involved in installing this on their server?
2. What all is involved in being able to create the reports?
3. Do I have to be able to connect to their server to create reports?
4. Can reporting services be installed on a developer edition of sql
services?
5. Are there any other requirements that I need to be aware of to do this?

Would I be better off going with a different product?

Thanks!