Thanks for your input...
My co-worker just read an article that indicated that the product should be
installed on a differnt machine than the SQL server. Did you do this? It
made it seem like the product may be a bit of a pig on resources. The
download for it is huge (150mb).
So you can develop using a web client but it is limited. I can definately
see the pro there of saving money for sure - That may be fine for an enduser
doing ad hoc stuff - but not like comprehensive enough for any real serious
report development work I take it then??
Brad
"BK" <bk******@hotmail.com> wrote in message
news:11*********************@i39g2000cwa.googlegro ups.com...
We are using SRS for some of our reporting needs, here is my take on
the results:
Pros:
It's easy to create reports, very easy. I spent a little time training
a quasi technical but mainly functional person and she was writing
reports in no time. She does all her work with the Web client, we
didn't install .Net on her machine (saved us a bunch of money!)
The users like the consistent and easy to understand interface to run
their reports
It reads the metadata in from SQL server when you create the data
model, so I didn't have to teach my power user anything about
relationships.
Cons:
The web client designer is limited.
If you make a change to the back end database schema, the model needs
to be regenerated.
We learned the hard way that it can be difficult or downright
impossible to recover a report sometimes if you make enough changes to
the back end.
HTH
