Presented by Paul Turley
Total Running Time: 205 min
In three technical presentations, report solution design expert and SQL Server MVP Paul Turley will show you how to get more out of Reporting Services using simple and advanced techniques. To get the most out of this unique training experience, you should be able to create basic reports for SQL Server 2008 R2 or 2012 with Report Builder 3.0, Business Intelligence Development Studio or SQL Server Data Tools.
SQL Server Reporting Services (SSRS) is Microsoft’s flagship reporting tool. A very capable and mature product introduced in 2004, SSRS is the go-to tool for all types of report designs. Report wizards and drag-and-drop features will get you started but the learning curve goes up if you need to design more than basic reports.
Using Report Builder 3.0 or the Visual Studio report designer, it’s fairly easy to create basic reports with no programming and only fundamental technical skills. Sure, easy reports are easy to design if you keep things simple. But if you need to build highly functional reports, you need to know how to write and use expressions. With some essential expression skills, you can take your report designs to the next level and give your business powerful reporting and analytic capabilities. Using these skills and design patterns, you can:
- Use parameters to drive dynamic report features with selectable table columns, chart elements and data measures.
- Conditionally visualize data elements to highlight threshold values and outliers; using color, size, fonts and icons.
- Build one report to visualize and format data in different ways, based on a variety of requirements and conditions.
After you have mastered expression basics, you can apply the same techniques in more advanced and creative ways, such as:
- Define custom drill-through targets, allowing users to navigate to different detail reports under different conditions.
- Create one report with dynamic filtering that responds to user-interaction.
Instead of having many different reports for all of your user needs, wouldn’t it be great if just a small number of reports were flexible enough to meet the needs of different business users? That would make the choice easier for users with fewer reports to maintain.
Have you ever created a report that doesn’t export to Excel in a format that works for the user? How would it be if the report were smart enough to know how it was being viewed or exported—and formatted itself accordingly? You can do that with expressions.