Re: Multiple Server Reporting
- From: "Jéjé" <willgart@xxxxxxxxxxxxxxxxx>
- Date: Fri, 8 Jul 2005 23:43:29 -0400
Centralize data is the better solution.
maybe there is some data to copy, but any query is local, so the response
time is good.
also, you can retrieve data for your reports only instead-of detailed
information.
"ERS Developer" <ERSDeveloper@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C501637B-D71F-4F72-AF62-B06BBED83A8E@xxxxxxxxxxxxxxxx
> Hi There,
> I got a generic DW question.
> Let me preface this
> I need to design a report that displays data for 3 branches of same
> companies, Branch A ,Branch B and Branch C. The problem is that each
> Branch
> has their own distinct server and database. The schema is identical
> between
> them, just
> different data in each.
>
> The report is identical for each Branch, the only different is that the
> report needs to pull data from all the three Databases A,B,C to display
> the
> report data for that Company as an aggregated view and Also data for each
> branch individually.
>
> How can I design the report or setup the data source.
>
> 1) One possible option I guess would be to create a Linked Server and
> Distributed view that combines data from identical tables in 3 databases,
> and
> use that view as the datasource in the report.
>
> 2) Other option is moving data to the centralized server and report from
> that,
> which would cause data redundancy both at local branch and at centralized
> server and huge vloume of data movement and keeping track of data.
>
> Just looking for what others have done in similar circumstances so I don't
> spend multiple days architecting the wrong approach.
>
> Thanks!
> S
>
.
- References:
- Multiple Server Reporting
- From: ERS Developer
- Multiple Server Reporting
- Prev by Date: Multiple Server Reporting
- Next by Date: Re: Multiple Server Reporting
- Previous by thread: Multiple Server Reporting
- Next by thread: Re: Multiple Server Reporting
- Index(es):
Relevant Pages
|
Loading
