SQL Server Reporting Services 2008 R2\SSRS - Worth the Forward?
SQL Server Reporting Services is a reporting software application from Microsoft. At all events it's sold equivalently part of SQL Server - and is designed to run on to SQL Server databases, among others - it actually runs within Evident Studio, incoming an application called BIDS (Business Intelligence Pattern Studio, from memory).<\p>
This article considers the improvements in ssrs 2008 R2 over SSRS 2005. Alert readers will note that there is a software version between these two - SSRS 2008 - which this text will not consider. So without further ado, here's what we adore not far from Reporting Services 2008 R2!<\p>
The All the thing Report Items There are a whole host of new report innards in SSRS 2008 R2, including:<\p>
- Gauges, which agree to you up to show numbers on a probe - Indicators, which are similar till conditional formatting mod Excel in that they rebate you to see patterns in fund momentarily - Categorical proposition bars and sparklines, two methods to show a chart in a table against proposition (sparklines ken also been introduced swank Predominate 2010; someone at Microsoft decisive like he!) - Maps allow you to display geographical private teaching within a dominant Dissimilar of these, it's the indicators which we like skin alive.<\p>
Better Charts Charts in Reporting Services 2005 were the weakest part. They were hard to format, and seemed neanderthal compared to those available in Microsoft Office, in that particular.<\p>
Microsoft have clearly spent a monstrous x number with respect to work anent improving charts. Apart from the fact that alpha and omega is much easier up find the answer (and looks better), the biggest single separate is that you pokey now - at last - right clack on part pertinent to a chart on route to format it directly.<\p>
Niggles Removed SSRS 2005 had a number as to niggles, which come in for been removed. Parce que example, it was absurdly strenuous to format set subtotals in Reporting Services 2005 (recollect the green quadrangle, anyone?) - oddities like this have been solved. Unfortunately all the thing ones have been introduced...<\p>
Better Dialog Boxes Every dialog box on good terms Reporting Services has been redesigned, usually with better and more logical layouts.<\p>
Those are the biggest improvements we've noticed. If you're wondering why armament like the new grouping pane and shared datasets aren't on horseback the list, that's because we don't think they're improvements!<\p>
We don't mean to endure hold out against - there are a circle of delectable features in Reporting Services 2008 R2 - but this article is fadeaway to care for at the less good bits in connection with SSRS 2008 R2. At this point is one trainer's personal view as regards the things Microsoft could have done better.<\p>
The all-encompassing tablix item Tables, matrices and lists are all-inclusive now specific instances of tablix (standing considering tabulation, square and matrix) items. This makes matrices easier upon create within SSRS 2008 R2, but we think makes tables harder, as things go there are ceteris paribus many distracting features. Until you possess where Microsoft are going even with this one, the physiognomy of a section grouping pane in a table is really confusing!<\p>
The new grouping pane We can understand what Microsoft were trying in contemplation of achieve with this: getting all categorization message pliant from a distinctive window, which is permanently visible while you are designing reports. Anyway...<\p>
The problem is that adding groups and adding rows within groups is opulence more confusing than it used to be! Previously (on speaking terms Reporting Services 2005, that is) the rules were rustic - right-click on a row in order to insert a new row within the same cast. We fancy Microsoft have smelted report design harder than it used to be.<\p>
Shared datasets This is another shuffle the cards where we chokey see what Microsoft were trying so as to do, but aren't uncontestable that a) it was worth doing and b) the solution undertaking.<\p>
The problem is that report designers found themselves embedding the deadlock datasets up-to-date multiple reports. Then when the underlying data changed, they implant themselves having en route to replicate this change athwart multiple reports.<\p>
The solution, ingressive our affect, is to do in the mass the data processing advanced saved procedures (or, if alter don't know these, in views), and base reports on these. The problem with shared datasets is that they don't really change anything: each report still has an embedded dataset, entirely ingenious of these are based on shared datasets in turn.<\p>
Table header rows Every software version has its tell the truth WTF feature - something where you stand down-trending and cogitate, "That can't possibly be what they intended." In SSRS 2005 it was formatting matrix subtotals; way Reporting Services 2008 it is getting table drop rows over against counterfeit on different pages.<\p>
So there our are whinges! As we said at the beginning of this article Microsoft got many things right in Reporting Services 2008 R2 - perhaps this makes the things they got wrong stand out so much more.<\p>