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

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. :-(
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
DanielB said…
Thanks! Was looking for this...
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

Popular posts from this blog

SSIS Configuration to Configuration to Configuration Schema

I've gotten several requests to put down in writing the configuration schema that I use as the base of my SQL Server Integration Services framework. It contains a set of configurations: an indirect environment variable configuration, which points to an XML configuration file configuration, which points to a SQL Server configuration. I learned this configuration from the Project REAL Reference Implementation . If you're getting started with a BI implementation, I highly recommend that you download it for some great ideas and best practices. Steps to implement: 1) Create an environment variable on your machine with the name of SSIS_CONFIG_FILE and the value of: C:\SSIS\Config\MasterConfigFile.dtsConfig. 2) Create an SSIS configuration file at C:\ SSIS\Config\MasterConfigFile.dtsConfig with the line: <configuration valuetype="String" path="\Package.Connections[CONFIG_SERVER].Properties[ConnectionString]" configuredtype="Property"><configuredv

Execute SQL Task Designer Limit

After migrating a package from DTS to SSIS, I had a problem with an Execute SQL Task. I couldn't change any characters in the SQLStatement property; I couldn't add any new characters; I could delete characters, but not retype them! After googling several variations of "integration services" "read only" and "Execute SQL Task", I deleted about half of the entry in a fit of frustration. Lo and behold, I could type again. Apparently, there is limit on the size or number of characters that can be entered in the SQLStatement property. From my experimentation, I came up with a limit of 32767 characters. The interesting thing is that the restriction only seems to be on the designer. If you set the SourceType to "Variable" and use a variable that contains more than 32767 characters, the task will execute. Also, if you use the "Direct Input" SourceType and modify the package XML to set the SQLStatement longer than 32767 characters,

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