Is MS Reporting Services suitable for stand-alone reports?
- by JMarsch
Hello all:
I work for a ISV. Our product can use both SQL Server and Oracle as its back-end server. It includes a number of reports (currently in Crystal).
We are investigating moving to Micrsoft Reporting Services, but I'm beginning to think that it's a bad idea.
We want for our reports to look and feel as though they are a part of our application, and we will not require SQL Server (the customer can choose Oracle).
Although I see the reporting services supports a stand-alone mode (RDLC), the boundry between what requires SQL server and what doesn't looks extremely ambiguous. (example, the stand-alone report builder appears to require SQL Server, most of the documentation appears to be part of SQL Server's documentation)
It looks to me like if I want to keep my application DB-agnostic, I had better steer clear of Reporting Services. Have I missed the boat here?