Report Model as datasource in ordinary report

I think the report model concept is great and it works well for the report
builder. Can a report model or a data source view be used as a datasource for
ordinary reports? We have a large number of reports built upon complex
relational queries (join join join join...), but pretty much the same query
for all the reports. One way of solving this is by building an olap cube, but
the thing is that all this reports are automaticly genererated from a
"backroom" database for quality checking and then all the data is loaded into
a final datawarehouse. But maybe it's possibel to do this without a cube in
the backroom.OK, I've figured it out myself. A report model can definitly be the data
source for a report and it works very well, actually!
"Erik Hedlund" wrote:
> I think the report model concept is great and it works well for the report
> builder. Can a report model or a data source view be used as a datasource for
> ordinary reports? We have a large number of reports built upon complex
> relational queries (join join join join...), but pretty much the same query
> for all the reports. One way of solving this is by building an olap cube, but
> the thing is that all this reports are automaticly genererated from a
> "backroom" database for quality checking and then all the data is loaded into
> a final datawarehouse. But maybe it's possibel to do this without a cube in
> the backroom.|||I didn't think that it could be, can you clue me in?
"Erik Hedlund" <ErikHedlund@.discussions.microsoft.com> wrote in message
news:EB83FAA1-FCE7-4A89-8125-18FEB3C71489@.microsoft.com...
> OK, I've figured it out myself. A report model can definitly be the data
> source for a report and it works very well, actually!
> "Erik Hedlund" wrote:
>> I think the report model concept is great and it works well for the
>> report
>> builder. Can a report model or a data source view be used as a datasource
>> for
>> ordinary reports? We have a large number of reports built upon complex
>> relational queries (join join join join...), but pretty much the same
>> query
>> for all the reports. One way of solving this is by building an olap cube,
>> but
>> the thing is that all this reports are automaticly genererated from a
>> "backroom" database for quality checking and then all the data is loaded
>> into
>> a final datawarehouse. But maybe it's possibel to do this without a cube
>> in
>> the backroom.|||Create a data source, a datasource view and a report model and deply it to
the report server.
Create a report and select report model as the data source and specify a
connectionstring for it. Example:
server=http://localhost/reportserver;datasource=/Models/name of report model
And then your on!
"Steve MunLeeuw" wrote:
> I didn't think that it could be, can you clue me in?
> "Erik Hedlund" <ErikHedlund@.discussions.microsoft.com> wrote in message
> news:EB83FAA1-FCE7-4A89-8125-18FEB3C71489@.microsoft.com...
> > OK, I've figured it out myself. A report model can definitly be the data
> > source for a report and it works very well, actually!
> >
> > "Erik Hedlund" wrote:
> >
> >> I think the report model concept is great and it works well for the
> >> report
> >> builder. Can a report model or a data source view be used as a datasource
> >> for
> >> ordinary reports? We have a large number of reports built upon complex
> >> relational queries (join join join join...), but pretty much the same
> >> query
> >> for all the reports. One way of solving this is by building an olap cube,
> >> but
> >> the thing is that all this reports are automaticly genererated from a
> >> "backroom" database for quality checking and then all the data is loaded
> >> into
> >> a final datawarehouse. But maybe it's possibel to do this without a cube
> >> in
> >> the backroom.
>
>sql