Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XS✔ ◾ 🚚 Migrated rule - Do you know when to use reporting services #7543

Merged
merged 2 commits into from
Dec 14, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
46 changes: 46 additions & 0 deletions rules/when-to-use-reporting-services/rule.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
type: rule
archivedreason:
title: Do you know when to use Reporting Services?
guid: d6d27c88-7697-436e-a66a-1d82287664c2
uri: when-to-use-reporting-services
created: 2023-12-11T12:38:33.0000000Z
authors:
- title: Jeoffrey Fischer
url: https://ssw.com.au/people/jeoffrey-fischer
related:
- customization-do-you-know-which-version-of-sql-reporting-services-and-visual-studio-you-are-using
redirects: []

---

<!--endintro-->

From our experience, we have discovered these things about Reporting Services:

### Cons

* Parameters - you are forced to use built-in controls.
* Query string - when you change the parameters and refresh a report, the values do not appear directly in the query string, making it hard to copy/paste URLs.
* Can't separate SQL into a strongly-typed dataset or middle-tier object like in ASP.NET.
* There are potential difficulties with the deployment of RS reports and the exposing of them. However, once we have the infrastructure...
* Not able to work natively with modern .NET.

### Pros

* You can develop read only reports faster in Reporting Services than ASP.NET.
* Maintenance with RS is easier than ASP.NET, as with most cases you don't have to write any code.
* Flexibility with groupings and totals is easier. In ASP.NET you would need to iterate through the DataSet, keeping variables with the totals.
* Parameters are built-in. In ASP.NET there is code.
* Drilldown interactivity. In ASP.NET you need to code up a treeview.
* Users can have reports automatically emailed to them on a schedule.
* Users can export natively to PDF and XLS, plus a variety of other popular formats.

Nowadays, better technologies are used to handle reports. Examples include

* Power BI: cloud-based solution that provides visually appealing reports and dashboards.
* HTML based reports: HTML frameworks have evolved significantly, making it quick and easy to make great reports.

For a more detailed comparison between reporting solutions, take a look at our [Guidelines for Report Solutions - Web Clients](https://www.ssw.com.au/ssw/Standards/DeveloperDotNet/guidelinesforreportingwebclient.aspx).

![Figure: Reporting Services has built-in support for PDF/XLS export and can be embedded in your ASP.NET pages](RSRulesUseRS1.gif)