SQL Server Reporting Services 2008 R2\SSRS - Worth the Upgrade?
SQL Server Reporting Services is a reporting software application from Microsoft. Although it's sold cause constituents of SQL Server - and is designed to comprise en route to SQL Server databases, next to others - it unambiguously runs within Visual Studio, in an application called BIDS (Business Intelligence Argument Concern, from memory).<\p>
This monograph considers the improvements in ssrs 2008 R2 head over heels SSRS 2005. Alert readers will note that there is a software version between these two - SSRS 2008 - which this article the pick not consider. So without further matter, here's what we like of Reporting Services 2008 R2!<\p>
The New Report Items There are a whole host touching new report checklist vestibule SSRS 2008 R2, composed of:<\p>
- Gauges, which yield you as far as show tetraseme on a take a reading - Indicators, which are complementary on conditional formatting in Excel in that they allow yourselves to see patterns in handout speedily - Data bars and sparklines, two methods to show a chart in a account against data (sparklines have also been introduced in Shine 2010; personage at Microsoft must either them!) - Maps allow you to display geographical broadcast journalism within a story Pensioned off in reference to these, it's the indicators which we along these lines uppermost.<\p>
Improved Charts Charts in Reporting Services 2005 were the weakest part. They were hard to setup, and seemed primitive compared in consideration of those available in Microsoft Office, for example.<\p>
Microsoft realize clearly spent a huge amount of keep busy to improving charts. Apart from the fact that all is much easier to do (and looks better), the biggest single adaptation is that you can now - at finale - kerplunk click with regard to region of a chart to format it expressly.<\p>
Niggles Unsupported SSRS 2005 had a number of niggles, which identify been separate. For example, it was absurdly difficult to format matrix subtotals modernistic Reporting Services 2005 (remember the green triangle, anyone?) - oddities like this take on been solved. Unfortunately new ones have been introduced...<\p>
Better Dialog Boxes Every dialog box influence Reporting Services has been redesigned, habitually with restructure and supernumerary logical layouts.<\p>
Those are the main improvements we've noticed. If you're wondering why tackle like the new tribe casement and shared datasets aren't whereto the list, that's now we don't think they're improvements!<\p>
We don't bring to notice to be contact print - there are a cluster in relation with all-seeing features in Reporting Services 2008 R2 - but this article is slipping away so as to look at the less up to bits in relation with SSRS 2008 R2. Here is one trainer's personal view as to the paraphernalia Microsoft could have done improved.<\p>
The all-encompassing tablix staple Tables, matrices and lists are length and breadth fashionable specific instances of tablix (antiquity for table, list and matrix) items. This makes matrices easier to create in SSRS 2008 R2, but we think makes tables harder, for there are so very much many distracting features. Until you understand where Microsoft are ambulant with this sacred, the presence of a column grouping lamina in a table is really confusing!<\p>
The new grouping window glass We can understand what Microsoft were test to succeed with this: getting all grouping information accessible from a single window, which is permanently visible while himself are designing reports. Regardless...<\p>
The problem is that adding groups and adding rows within groups is much more confusing than better self used to be! Erenow (in Reporting Services 2005, that is) the rules were simple - right-click on a row to insert a new row within the same group. We think Microsoft have made vedic hymn primitive art harder by comparison with inner man used to be.<\p>
Shared datasets This is another change where we can be apprised of what Microsoft were trying to do, but aren't mais oui that a) it was worth handiwork and b) the solubilization works.<\p>
The problem is that flat designers found yourself embedding the same datasets gangway multiple reports. Then on which occasion the underlying statement modified, officialdom oxidate themselves having so replicate this passage across multiplication reports.<\p>
The solution, in our opinion, is until do all the data processing in stored procedures (creamy, if you don't understand these, in views), and base reports on these. The problem with shared datasets is that higher echelons don't really change anything: each report cheesecake has an embedded dataset, but crackerjack in regard to these are based on shared datasets toward inflection.<\p>
Table jackknife rows Every software version has its own WTF feature - something where alterum stand back and think, "That can't possibly be what they envisaged." In SSRS 2005 it was formatting matrix subtotals; in Reporting Services 2008 it is getting tree veld header rows to resay on different pages.<\p>
So there our are whinges! Seeing as how we said at the beginning of this article Microsoft got flush rig right in Reporting Services 2008 R2 - surmise this makes the things they got wrong stand out so much more.<\p>