Skip to main content

Where is my Data Tab?

I’ve recently had the pleasure of diving into Reporting Services 2008 RC0, and I’m amazed at the difference in the design environment from SSRS 2000/2005! To give a comparison of the designer, I took a look at the BIDS Reporting Services project. Overall, I think this version is more slick and more user-friendly (once I find everything again :) ) than its predecessor.

To begin, there is no longer a Data tab in the main frame of the design environment. You can find your DataSets and Fields on the “Report Data” window on the left side of your designer. If you lose your Report Data window, click the View menu > Report Data, or just select Ctrl-Alt-D. Also joining the new Report Data family are Report Parameters, originally found on the Report menu, and Fields, originally on its own window.

A look at the new RS would be remiss without mentioning the new Tablix control. From the toolbox, you still select a Table, Matrix, or List control, but these are templates for the Tablix control that provide you with the expected layout. As soon as that control has landed on your Design window, the properties and group menus look the same. In fact, the menu option to view properties is labeled “Tablix Properties…”. It is easy to see how the rows and columns are utilized from the icons displayed to the left or top of the textboxes.

Instead of Groups being included in the properties window of each control, they are now displayed on the report itself. This option can be toggled by right-clicking on the report and selecting View > Grouping. By selecting the desired control in your design window, you can immediately see the groups for that control.

All of the property windows have been overhauled. Is it just me, or do the new property windows remind you of the Dundas Controls property windows?

I’ll be posting more thoughts and trials on Reporting Services 2008 as I dig deeper into the new system!

Version: SQL Server 2008 RC0
Labels:

Comments

Anonymous said…
I see that you can use the Report Data window to make new data tabs but I don't see that it's better. I lost the "intellisense" colors that it was giving my MDX in the BIDS 2005. It's 100 times harder to do MDX now. What a bummer. :-(
April 30, 2009 at 2:58 PM
Jessica M. Moss said…
Hi there,

I like the data tab because I can find every piece of information that I want to bring into my report in one place. The error color coding for MDX is going to be part of a different component, the MDX Query Builder. I typically write my MDX queries in SSMS and just paste them into the designer, so it hasn't affected me that much. If it's something that you feel is important, I recommend you file a change request at Microsoft's Connect site.

Best,
Jessica
May 13, 2009 at 7:08 PM
DanielB said…
Thanks! Was looking for this...
October 27, 2010 at 11:29 PM
Anonymous said…
Jessica, thanks for this tidbit (Ctrl + Alt + D)....lifesaver.

I have wasted an embarrassing amount of time trying to get it back.

Cheers, Andy
November 16, 2010 at 3:59 PM
Post a Comment

Popular posts from this blog

Upgrading your SSIS Management Framework: Part 3

At this point, you understand the options for moving an SSIS framework to the latest version of SSIS, and you've upgraded the logging portion of the framework using a hybrid approach.  The final step in the framework upgrade is handling your configurations.  Let's walk through an existing configuration implementation and how you can upgrade it by combining your existing implementation with the standard SSIS framework. Overview A typical "old-school" configuration scheme is described in the SSIS PDS book or in this blog post here: http://jessicammoss.blogspot.com/2008/05/ssis-configuration-to-configuration-to.html .  Starting in SSIS 2012, the configuration scheme uses environments and parameters when using the Project Deployment Model, as discussed here: http://msdn.microsoft.com/en-us/library/hh213290(v=sql.110).aspx . In both scenarios, the core ideas in a configuration scheme are: Provide the ability to move packages through environments without having
Post a Comment
Read more

Manipulating Excel Spreadsheets in SSIS

Tom, an attendee at last weekend’s SQLSaturday Olympia , asked me how to refresh a spreadsheet from within SQL Server Integration Services. My first thought was to turn on the connection’s “Refresh data when opening the file” option in the spreadsheet itself and avoid the situation entirely; however, this may not always be a viable solution. Here are the steps to perform the refresh from within an SSIS package. First, ensure that Microsoft.Office.Interop.Excel is registered in the GAC. If not, install the 2007 Microsoft Office system Primary Interop Assemblies . This will need to be done on any machine where you plan on running this package. Next, create a script task in your SSIS package that contains the following code (include your spreadsheet name): Imports System Imports System.Data Imports System.Math Imports Microsoft.SqlServer.Dts.Runtime Imports Microsoft.Office.Interop.Excel Public Class ScriptMain Public Sub Main() Dts.TaskResult = Dts.Results.Success Dim excel
52 comments
Read more

Reporting Services 2008 Configuration Mistake

To start working with the management side of SQL Server Reporting Services 2008, I decided to set up a report server and report manager. Unfortunately, I made a mistake while setting up my configuration that left me a little perplexed. Here are the steps I took to cause, track down, and solve the issue. Problem: I began by opening the Reporting Services Configuration Manager from the Start Menu. I clicked through each of the menu options and accepted the defaults for any question with a warning symbol, since warning symbol typically designate an action item. After two minutes, all of the warning symbols had disappeared, and I was ready to begin managing my report server. Unfortunately, opening up a browser and trying to open up the report manager resulted in the dreaded " The report server has encountered a configuration error. (rsServerConfigurationError) " message. Sherlock-ing it: I put on my sleuthing hat and went to the log file directory: C:\Program Files\Microsoft
45 comments
Read more