June 29, 2010 at 11:42 am
Greetings,
It's possible to create reports using Reporting Services, and it's possible to create reports using ASP.NET (either directly, or using the ReportViewer control to link to Reporting Services.) Also, there are charting capabilities available to both Reporting Services and ASP.NET.
Are there any guidelines, recommendations, best practices, etc., regarding why/when to use Reporting Services to develop and run reports, as compared to using .NET, or is it primarily a matter of preference?
Thanks,
Randy
June 29, 2010 at 11:47 am
Well, as far as I understand it, the report viewer is just, as you said, a link to Reporting Services, which means that the reports would have to be developed in Reporting Services. I am not aware of the fact that you can create reports natively within .Net. There are 3rd party controls (DexExpress, Infragistics, Telerik, etc.) that you can use to embed charts and other reports into .Net pages.
I could be wrong...someone please correct me, if I am.
Thanks...Chris
June 29, 2010 at 1:02 pm
I guess I am hearing about MS Charting Controls (apparently similar to the controls available within Reporting Services) and am wondering "Why not just use the Charting Controls with .NET apps and forget about using Reporting Services". I'm fine with using Reporting Services, I'm just trying to figure which is the tool to recommend to developers here.
June 29, 2010 at 2:04 pm
Hmm...I guess it depends on what you want to do.
This is a tutorial on using it in .Net.
http://www.4guysfromrolla.com/articles/072209-1.aspx
I guess it also depends on how you want to structure your environment/application. For centralization of reports, use Reporting Services. If you really don't care, I guess you can just implement the reporting/charting in .Net application.
Hope that this helps...thanks.
Chris
June 29, 2010 at 4:48 pm
As has been said before, it depends....
SQLRS has many potential benefits - scheduled reporting, emailing, cahed report data, execution history to name a few....
ASP.NET could be more flexible but you would have to develop the reporting structure and any features you liked from SQLRS yourself, and maintain the code, upgrade the code etc....
I think you can tell - I prefer SQLRS.... 😎
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply