Direct Reports : Reporting Services

Transmissions from the Satellite Heart (What's up with Report Builder?)

bwelcker — Wed, 12 Dec 2007 00:33:58 GMT

Hopefully, you have gotten a chance to work with the latest CTP of SQL Server 2008 Reporting Services . But if you have, you may be a bit puzzled by the report design options in the CTP. Specifically: Report Builder looks just like it did in SSRS 2005....(read more)

Tribal Thunder (SharePoint White Papers Available)

bwelcker — Tue, 11 Dec 2007 10:29:00 GMT

After many months of working on getting them posted, I'm excited to let you know that two whitepapers on the integration between SQL Server Reporting Services and SharePoint are now available. SQL Server 2005 Integration with Microsoft SharePoint Products...(read more)

Everybody (Why Leave IIS?)

bwelcker — Tue, 04 Dec 2007 23:34:03 GMT

If you have gotten a chance to try an early build of SQL Server Reporting 2008 Reporting Services, you know that one of the changes in the product is the removal of the Internet Information Services (IIS) dependency. I have gotten some questions about...(read more)

Younger Than Yesterday (ReportViewer in VS 2008)

bwelcker — Mon, 26 Nov 2007 20:04:53 GMT

As most of you probably know by now, Visual Studio 2008 is now available. What you might not have noticed is a new version of the ReportViewer control and local /embedded report editing experience. Included with VS 2008 are the following new features:...(read more)

Marquee Moon (Field References in Page Headers and Footers)

bwelcker — Wed, 20 Jun 2007 09:57:00 GMT

One of the questions that I get often is about putting database fields in their SSRS report page header and/or footer. Note that putting fields in the page header and footer is not the same as putting a data region in these sections. Because of the impact...(read more)

When I Was Born for the 7th Time (Thoughts from TechEd)

bwelcker — Sat, 16 Jun 2007 21:46:00 GMT

Last week I attended TechEd in Orlando, Florida . Here are my thoughts on the event. This year was TechEd's 15th anniversary. I realized on the way down that I was attending my 10th consecutive TechEd. When I started attending, TechEd was about 2,000...(read more)

Dreamy (Reporting Services at TechEd)

bwelcker — Mon, 04 Jun 2007 19:28:00 GMT

Unlike previous years, I decided not to attend the first day of TechEd. This means that I missed BobMu's keynote but you can read about the details from many of the TechEd bloggers.

If you read the press release from TechEd today, we announced the official name for the next release of SQL Server - SQL Server 2008 (so long, Katmai). You can also download the first CTP. While I would encourage you to try some of the new features in the CTP, you are going to be a little disappointed if you are looking for new Reporting Services features. We have scheduled our first set of new features for the next CTP - so stay tuned for a few more months. If you attend one of our TechEd sessions, you will get a preview of what is coming.

Our second big announcement from TechEd was that we have acquired the data visualization products of Dundas Software. Many of you have been using the enhanced chart for Reporting Services along with the gauge and map custom report items. We realized the importance of data visualization components for reporting so we purchased this codebase for inclusion in future versions of SSRS. We are working on the integration right now so I can't promise how much will make it into SQL Server 2008.

As for TechEd itself, I'm heading out tomorrow. Feel free to stop by the Business Intelligence part of the Learning Center and say hi. If you are looking for some Reporting Services related content, try these sessions:

BIN 305 - Applied Microsoft SQL Server 2005 Reporting Services
DAT 201 - The Next Release of Microsoft SQL Server: Overview
BIN 202 - Third Annual Business Intelligence Power Hour
BIN04-TLC - Reporting Services Rendering Tips and Tricks
BIN 306 - Microsoft SQL Server 2005 Reporting Services: Advanced Report Design
BIN 318 - Reporting Services Futures: Report Authoring for Information Workers
BIN05-TLC - Integrating Microsoft SQL Server 2005 Reporting Services and Microsoft Office SharePoint Server 2007
BIN15-TLC - Reporting Services Programmability
BIN 306R - Microsoft SQL Server 2005 Reporting Services: Advanced Report Design

At the End of Paths Taken (Modifying Where Clause when All Parameter Values are Selected)

bwelcker — Sat, 19 May 2007 23:32:00 GMT

With the return of “Select All” in Service Pack 2, all multi-value parameters allow the user to pick all of the available values. But what if you want to remove the predicate from your WHERE clause instead of generating a long set of values in the IN predicate?

You can accomplish this is via an expression-based query and an internal parameter.

First, create a second parameter in your report. It should be have a new name, multi-valued, use the same valid values query and the default values set to the valid values query as well. In addition, mark the "internal" flag in the parameters dialog so it is not displayed to the user.

Next, change your main report query to an conditional expression that compares the number of selected values to the number of available values (which will always be selected in the new parameter). For example:

="SELECT Hour, Month, Year, Username, Sitename, Cookie FROM dbo.GlobalIISLog " & IIF(Parameters!ComputerName.Count = Parameters!AllComputerNames.Count,"", " WHERE (sComputername IN (@ComputerName))")

I have attached a sample report that demonstrates this technique.

Watusi (SSRS Management Tools Changes for Katmai)

bwelcker — Tue, 24 Apr 2007 17:52:00 GMT

For Katmai we are considering the removal of namespace management (folders, reports, data sources, models) from the Reporting Services Add-in for SQL Server Management Studio (SSMS). In other words, we are considering removing the 'Home' folder under the Reporting Server node in SSMS.

Why the change?

Customer feedback and usage data indicates that Report Manager and/or SharePoint are the tools of choice for managing the Report Server namespace, rather than the SSMS add-in. The design constraints of SSMS mean that any new namespace functionality is significantly expensive to implement, specifically adding support for the namespace in SharePoint integrated mode. For Katmai we want to invest in SharePoint and Report Manager for namespace management and focus on SSMS as a server-level management tool.

This means that the namespace management functions that are not available in Report Manager (Model ClickThrough and Model Item Security) will be added to Report Manager (they are already in SharePoint). Job Management, configuring System properties, and administering Roles will be moved to SSMS. In addition, SSMS will be updated to work in SharePoint mode.

If you have feedback about these changes, please feel free to comment.

Pocket Symphony (Enabling SSRS Feature in non-default Site Collections)

bwelcker — Thu, 22 Mar 2007 06:42:00 GMT

After installing the Reporting Services Add-in for Integration with SharePoint, you may find that the Reporting Services features are not visible in your SharePoint web sites. Why does this happen? Because when the add-in is installed, it is only activated for the sites in the default Site Collection.

Steps to resolve:

Bowse to the 'Home' or root URL of the site collection.
Click on Site Actions -->Site Settings --> Site Collection Features.
Choose the "Reporting Services Integration" feature, under the list of features for Site "Collection Features".
Press the "Activate" button.

Note: You will need to be owner of the site collection in order to view the "Site Collection features" link.

Candy Apple Grey (Installing SSRS and Windows Vista)

bwelcker — Tue, 20 Mar 2007 02:34:00 GMT

It's a bit tricky to get Reporting Services (including the report server that comes with SQL Express with Advanced Services) to work on Windows Vista. The key is to turn on the right set of IIS components in the "Turn Windows features on or off" tool in the Vista control panel. Here is the list of required IIS features you need to add for Reporting Services to work:

Web Management Tools

IIS 6 Management Compatibility
IIS 6 WMI Compatibility
IIS Metabase and IIS 6 configuration compatibility

World Wide Web Services

Application Development

.NET Extensibility
ASP.NET
ISAPI Extensions
ISAPI Filters

Common HTTP Features

Default Document
Directory Browsing
HTTP Redirection
Static Content

Security

Windows Authentication

Note that IIS7 in Vista Home Premium does not include Windows Authentication functionality so it will not work with SSRS.

You will get a compatibility message when you start to install SQL Server 2005. This is to let you know that you will need to install SQL Server 2005 Service Pack 2 after the installation finishes. You should also read Section 5.5 of the SQL Server 2005 Readme (Reporting Services Considerations for Windows Vista) for known issues and limitations.

We Were Dead Before the Ship Even Sank (SSRS Reports on SharePoint Lists)

bwelcker — Wed, 14 Mar 2007 06:11:00 GMT

Now that we have released the SSRS integration in MOSS 2007 / WSS in SQL Server 2005 Service Pack 2, people often ask whether they can build reports against data in SharePoint lists. Although this functionality is not built into SSRS, if you are willing to go pick up a 3rd party component, I have heard of several customers successfully using the Enesys RS data extension for SharePoint lists. If you want to go down the free software path, you might also check out this blog from Teun Duynstee. We will consider native support for lists in a future release.

Propeller (SP2 is Released!)

bwelcker — Mon, 19 Feb 2007 20:57:00 GMT

It's been a long time coming, but SQL Server 2005 Service Pack 2 is now available. See http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/servicepacks/sp2.mspx.

Roots and Crowns (Too Many Data Tools?)

bwelcker — Sun, 18 Feb 2007 05:14:00 GMT

Sometimes I'll get a question like "Why would I use Reporting Services when I can use Excel?" or "Why does Microsoft have so many tools for building reports?" The underlying assumption behind these questsions is that a limited number of applications should be are able to work with data. IMHO, I think that working with data is something that should be included in every application, not just limited to "BI tools".

I look at interacting with data as a capability similar to formatting text or spell checking. No one asks "Why do I need to format text in PowerPoint when I have Word?" or "Who would need a spell checker in OneNote?". Applications can share a common set of capabilities but work in very different ways to achieve different results. Can you build a presentation in Word? Sure, but it's not optimal. Could you use PowerPoint to make a network diagram? Sure, but once again, it's not optimal. Anyone who has used Report Designer or Report Builder know that they feel different from Excel and make certain types of outputs easy to do (say, repeating groups of forms). At the same time, if someone feels comfortable with a working with a spreadsheet, they shouldn't feel compelled to use another tool just because they want to add data to it.

What should be common is how people work with data and what services they get around that data. Having every application work with data in a different way is like having every application with it's own way to edit text. In this area, we have a lot of work to do. If we can unify around a common set of experiences with data, I expect very soon that these features will show up everywhere.

Wincing the Night Away (Tips for SSRS in SharePoint Mode)

bwelcker — Mon, 05 Feb 2007 00:53:00 GMT

Here is some useful information about using SSRS in SharePoint Integrated mode (included with SP2):

Installing the SharePoint Add-In

If you plan to upgrade from a previous version of the add-in, you should uninstall the previous add-in then install the new one. After installing the new one, you will need to perform the RS configuration steps in SharePoint Central Administration again.
If you have trouble with the install, take a look at the log files. In addition to the MSI install log, the Add-In also creates another log file named RS_SP_<number>.log. Both logs are found in the "<Drive>:\Documents and Settings\<User_Name>\Local Settings\Temp" folder.
There is a known issue with the naming ReportServer.<culture>.resx files that are install as part of CTP3 in each SharePoint web sites' App_GlobalResources folder. After installing CTP3 this issue manifests itself as the following errors when you try to access any SharePoint web site:

Server Error in '/' Application.
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

To solve this, check the following in IIS Manager for each SharePoint web site:

Explore into <Web site>\App_GlobalResources

Do you see any Reportserver.<culture>.resx files (where culture is a string like EN / FR/ CS etc.)?

If yes, then delete all Reportserver.<culture>.resx except for ReportServer.resx file.

Deploying Reports to Report Server that is in SharePoint Mode

Use the updated Report Designer that ships with SQL 2005 SP2 CTP.
Deployment paths need to change for deploying to a SharePoint Document Library with settings something like this:

TargetDataSourceFolder: http://<MyServer>/<mySharePointsite>/<my_DataSource_Folder>/
TargetReportFolder: http://<MyServer>/<mySharePointsite>/<my_Report_Folder>/
TargetServerURL: http://<MyServer>/<mySharePointsite>/

If you see a login screen when deploying reports, inspect the web.config fle of the SharePoint web site for the following entry:

<location path="_vti_bin/ReportServer/ReportServiceAuthentication.asmx">
    <system.web>
      <authorization>
        <allow users="*" />
      </authorization>
    </system.web>
</location>

Make sure there is only one such entry in the web.config file. Delete any duplicates. Next retry deploying. This is a known issue in the CTP release that we are fixing for RTM.