Thanks,
~Bradabout damn time :P
It was a simple install ... very easy to work with once i figured out where the darn designer was hiding.. I think there needs to be better information on where to start the designer up. I spent a few hours looking through documentation. I have to say it will be nice to finally get away from using CR.NET or Access for a reporting solution.
Adminstration aspect is fairly straight forward as long as you read carefully before attempting to expose a report to the public.
Morgan|||i just ordered my copy...waiting to get my hands on it. we have huge reporting needs...not a lot of traffic but lot of different types of reports... :)|||I was using it in beta version & going to use final. My 1st impression could be found onhttp://www.aspalliance.com/339|||How about performance? Does it place a ton of additional load while the reports are running?
thx
bk|||"For eyes" not more than CR reports, but I didn't measure it.|||Just thought I'd post this article I came across at SQLServerCentral (note: you have to have a free membership to read the articles there, and I am in no way affiliatd with the site):Reporting Services Part I: Overview, Architecture and Installation by James Luetkehoelter. He will be following up that article with "Reporting Services Part II: Report Design".
Terri|||Its really bad that SQL Server reporting services needs VS.NET 2003 and not VS.NET 2002...
Is there a work around...|||You need VS.NET 2003 in order to use the Report Designer. The Report Designer is a friendly GUI that creates an report definition file in XML format. You could code this XML file by hand, you could look for a third party's GUI, or you could write one yourself if you are so inclined.
Terri
No comments:
Post a Comment