RS Question

Hi,
SO how does everyone here like Reporting Services for SQL? Any real
problems or bugs I should know about if I use it?
Thanks,
JJIt's a version 1 product from Microsoft, but a very good one. You have to
think of it as a reporting platform, not just a reporting tool. It's very
powerful, very well thought-out. The interactive capabilities are
fantastic. There are a few rough edges, some goofy rendering issues
(non-deterministic pagination, etc.), but so far it's working very well for
us, and it's only going to get better as new releases come out.
Cheers,
--
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"JJ" <JJ@.discussions.microsoft.com> wrote in message
news:EC688006-1EE0-47C1-8C75-07E8FC3D53EA@.microsoft.com...
> Hi,
> SO how does everyone here like Reporting Services for SQL? Any real
> problems or bugs I should know about if I use it?
> Thanks,
> JJ|||I suggest you buy the "Hitchhiker's Guide to SQL Server 2000 Reporting
Services" if you
decide to go with Report Services.
I just got it in and it's a must have so far.
David
"JJ" <JJ@.discussions.microsoft.com> wrote in message
news:EC688006-1EE0-47C1-8C75-07E8FC3D53EA@.microsoft.com...
> Hi,
> SO how does everyone here like Reporting Services for SQL? Any real
> problems or bugs I should know about if I use it?
> Thanks,
> JJ|||I really like it. There are a few quirks like ordering items in a table with
groups. You order the details at the table level and the groups and the
group level a little counter intuitive but once you figure that out it is
easy. IIF statements don't work well for eliminating nulls. Referencing
textboxes can be a little tricky(the expressions are case sensitive). For
our purposes, building parameterized reports for distribution over the
intranet, converting from CR/CE to RS has been a resounding succes. It
eliminated all the major problems (SP based reports crashing)we had with CR
and replaced them with a few small ones(no direct printing from browser).
Definitely not perfect for everyone but more than worth a look.
"Yoshi" wrote:
> I suggest you buy the "Hitchhiker's Guide to SQL Server 2000 Reporting
> Services" if you
> decide to go with Report Services.
> I just got it in and it's a must have so far.
> David
> "JJ" <JJ@.discussions.microsoft.com> wrote in message
> news:EC688006-1EE0-47C1-8C75-07E8FC3D53EA@.microsoft.com...
> > Hi,
> >
> > SO how does everyone here like Reporting Services for SQL? Any real
> > problems or bugs I should know about if I use it?
> >
> > Thanks,
> >
> > JJ
>
>|||You can find more info about RS here:
www.ReportingServicesFaq.com
And there is a RS Wiki community being built here:
www.ReportingServicesFaq.com/ow.asp
JJ wrote:
> Hi,
> SO how does everyone here like Reporting Services for SQL? Any real
> problems or bugs I should know about if I use it?
> Thanks,
> JJ|||Great if you want to do simple reports
but if you want a report containing say 12 sub reports
switching different ones in and out with seperate header or footers
then I suggest sticking with crystal for now. Until it matures a bit
Im sure eventually it will be a good product
"JJ" wrote:
> Hi,
> SO how does everyone here like Reporting Services for SQL? Any real
> problems or bugs I should know about if I use it?
> Thanks,
> JJ|||RS can handle complex reports. It all depends on what you think is complex
and what is the complexity. In your case it isn't the fact that there are 12
sub reports. It is the fact that you want to essentially modify the report
on the fly. RS does not handle that well. With version 2 you could modify
the report before handing it to one of the new controls. I'm not sure with
your scenario whether it would make sense even then. The problem being that
it looks like you want to modify the design of the report based on the data.
My guess here is that you had existing reports that acted this way and
wanted to duplicate it. In general I would stay away from that many
subreports and instead give the user drill through capability. Present the
user they need to see and have them click on a link that pulls up another
report for further information. Drill through is so easy and powerful.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stu" <Stu@.discussions.microsoft.com> wrote in message
news:A14DA2D9-3510-4E1C-A775-2544ACD8A2CB@.microsoft.com...
> Great if you want to do simple reports
> but if you want a report containing say 12 sub reports
> switching different ones in and out with seperate header or footers
> then I suggest sticking with crystal for now. Until it matures a bit
> Im sure eventually it will be a good product
> "JJ" wrote:
> > Hi,
> >
> > SO how does everyone here like Reporting Services for SQL? Any real
> > problems or bugs I should know about if I use it?
> >
> > Thanks,
> >
> > JJ