Link to home
Start Free TrialLog in
Avatar of friskyweasel
friskyweasel

asked on

Reporting Services 2005 - Shared Dataset

I've searched and seen this same question asked several times on EE, but I just have to ask again. Is there not some simple way to create a dataset (not a datasource) once, and then use that dataset in multiple reports without having to manually add it into each report by hand? I already saw someone posted that you can copy/paste the desired sections from the XML (view source) of the RDL file....but that's not really what I was looking for.

Is there still no built-in functionality in Reporting Services 2005 to accomplish this?
SOLUTION
Avatar of SQL_SERVER_DBA
SQL_SERVER_DBA
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of friskyweasel
friskyweasel

ASKER

yup that's true - but i guess it's the idea that you even have to "create" another dataset in the first place...even if that dataset is populated by a stored proc rather than hand-writing the sql every time.

If i have a drop-down filter that allows a user to select a color...and i know that filter will be used multiple times across my reports...i shouldn't have to create a dataset named "dsColorFilter" over and over if i know it will be used in every report

It's being a bit picky I know...but imagine when you have 40 and fifty reports to do...and 3 out of 5 filters/dropdowns on each report are actually common to all reports...you could save a lot of time if you could just create them one time and then re-use them.

I'll leave the question open for a while longer to see if there are any other ideas or something i'm missing here.
oh, I see you have a point...I don't think I can help you here but it is good food for thought.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thanks for your efforts guys - PFrog I think your suggestion probably comes the closest, but SQL Server DBS's is also viable - i'm going to do an 90/10 split