I’m well into the research for my new (and overdue) SQL Server Magazine article on Report Builder 2.0. Along the way I’ve discovered a couple of interesting bugs. It seems that if you choose to use the “Stored Procedure” command type you can indeed name a stored procedure, but the wizard won’t set it up correctly unless it has defaults defined for each of its parameters.
Incidentally, you had better be prepared for the wizard to execute this puppy (not just parse for signature) as the SP gets executed at least once if not several times in the process. I expect this would be a problem if the SP took seven and a half hours to execute…
I also discovered that even when defaults are defined, the wizards don’t properly map the query parameters the first time. Once the Dataset is created you have to go back to the DataSet properties and Refresh Fields. Tacky…
I’m still tracking down why stored procedures are not listed along with the Tables and Views in the Query editor… I expect it might be (another) Windows 7 rights issue.
hth
