February 2010 Archives

In Report Builder 2.0 one can open a report to edit and redeploy via a dialog that exposes the (rights-visible) Reporting Services catalog. This makes it easy to bring up a deployed report for editing.

In Visual Studio Reporting Services BI tools, you can’t. What you can do is first export the report by navigating to the report properties in Report Manager (General tab) click the “Edit” link, and save the report to an RDL file. Next, you have to “Add Existing Item” to the project and point to the saved RDL report. Why can’t the BI tools do the same as Report Builder 2.0?

In Report Builder 2.0 one can choose the Data Source by browsing the Reporting Services catalog.

In Visual Studio Reporting Services BI tools, you can’t. When you create a new BI project the BI tools should prompt for the RS catalog as it does with a CLR project. This way, when a new report project is created the developer could choose from a list of cataloged Shared Data Sources. This would preclude the need to guess at or research the shared data source name when creating a new report project.

I spent considerable time at the recent MVP Summit here in Redmond (Feb 16-19th) trying to get some answers to a number of nagging questions and issues that I and my customers keep asking. Windows Live Meeting (WLM) was high on the agenda. Ironically, several of the Microsoft employees with whom I spoke were fighting many of the same WLM issues but they could get no help at all because they didn’t have support accounts and could not get past the script-readers.

The company that hosts my monthly webinars (9-18 hours a month) hires a third-party company that hosts and records the Windows Live Meeting sessions. They and I have been unable to adequately address any of the following issues: (Updated Feb 22)

Updated Feb 4, 2010

I’m working on the labs for a new interactive webinar being hosted by Progressive. It’s tentatively scheduled for late April so I’m heads-down building the courseware. Unlike my “speak-only” webinars where I simply lecture and take questions, this series of six 90-minute sessions will encourage the attendees to work through a series of lab exercises that leverage the lectures and permit them to try to build and test SQL Server databases, SQL queries and reports using VB.NET and Report Builder 2.0.

In the course of creating these labs I’ve run across a number of issues that I would like to see Microsoft address in the next version of Report Builder. Frankly, I would not expect to see any work done on SQL Server 2010/2011 but I would like to see the following issue addressed after that:


Powered by Movable Type 4.21-en

About this Archive

This page is an archive of entries from February 2010 listed from newest to oldest.

January 2010 is the previous archive.

March 2010 is the next archive.

Find recent content on the main index or look in the archives to find all content.