Crystal vs SQL Server Reporting Services (SSRS)

Yahoo Archive
1
Crystal Reports will always have its place, IMO. Where SSRS shines is
with creating ASP dashboards and reports that export easier and generate
faster than Crystal Reports in most scenarios.



I would recommend fixing things in Crystal Reports for now. Let the
dust settle, catch your breath and then start adding bells and whistles
post implementation.



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Emily
Sent: Monday, November 08, 2010 8:54 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Crystal vs SQL Server Reporting Services (SSRS)





Hi everyone. For those of you who have knowledge of Crystal Reports and
SSRS I'd really like your opinion. A few people in our organization know
and use Crystal. Before moving to 9 we were told that we'd be able to
use SSRS for report writing and it would be TONS easier. We're a month
plus in to our implementation of 9 and we've been getting mixed info
regarding our ability to use SSRS. We're finding that some of our
reports don't work now since the conversion and I'm just trying to
figure out if I need to push getting SSRS up and running because of its
easy or if it really isn't that easy and I'm better off fixing things in
crystal. I appreciate your opinions.

Emily





[Non-text portions of this message have been removed]
2
Hi everyone. For those of you who have knowledge of Crystal Reports and SSRS I'd really like your opinion. A few people in our organization know and use Crystal. Before moving to 9 we were told that we'd be able to use SSRS for report writing and it would be TONS easier. We're a month plus in to our implementation of 9 and we've been getting mixed info regarding our ability to use SSRS. We're finding that some of our reports don't work now since the conversion and I'm just trying to figure out if I need to push getting SSRS up and running because of its easy or if it really isn't that easy and I'm better off fixing things in crystal. I appreciate your opinions.

Emily
3
Not sure you gain much with using SSRS for Epicor reports – dataset generation method is identical to Crystal and in fact, when you run a SSRS report you get the Crystal XML copied over to the SSRS directories and executed from there.
Regarding the report builder, think it is a little simpler to use than Crystal but has its limitations in complex design – Crystal is still better.
However, if you are a SQL implementation you can write your own reports and combine them into one uniformed look – you can place your reports right on the Epicor 9 menu to look like an Epicor report.
There are still many bugs in the rollout of SSRS reports and not all work correctly. Think you will see a phase out of Crystal over the next 2-5 years and move to SSRS reports –
Motty


--- In vantage@yahoogroups.com, "Emily" <emverbeke@...> wrote:
>
> Hi everyone. For those of you who have knowledge of Crystal Reports and SSRS I'd really like your opinion. A few people in our organization know and use Crystal. Before moving to 9 we were told that we'd be able to use SSRS for report writing and it would be TONS easier. We're a month plus in to our implementation of 9 and we've been getting mixed info regarding our ability to use SSRS. We're finding that some of our reports don't work now since the conversion and I'm just trying to figure out if I need to push getting SSRS up and running because of its easy or if it really isn't that easy and I'm better off fixing things in crystal. I appreciate your opinions.
>
> Emily
>
4
Emily,



I saw your earlier post about losing your IT person to medical leave.
If you are short handed, then I would especially be sure to stick with
Crystal.



You already have the expertise inhouse it sounds like and more
importantly - the reports.



Most of the reports do not yet exist under version 9 for SSRS (this is
according to the Epicor folks at Perspectives) so you would need to
develop everything from scratch.



Stick with what you know until you get out of your choppy waters.



John



[Non-text portions of this message have been removed]