On Wed, May 23, 2012 at 5:11 PM, Herouth Maoz wrote:
> A replication solution is not very good, either, because of course I can't
> define indexes differently, I don't want *all* transactions in all tables to
> be sent, and also, because I may want to cross reference data from different
> syste
On 23/05/2012, at 18:54, Bartosz Dmytrak wrote:
> hi,
> my suggestion is to redesign reporting database to fit reporting specifics
> (e.g. brake normal form of database, in some cases this will speed up
> reports). Than you can use some ETL tool to sync production and reporting.
> Good thing i
hi,
my suggestion is to redesign reporting database to fit reporting specifics
(e.g. brake normal form of database, in some cases this will speed up
reports). Than you can use some ETL tool to sync production and reporting.
Good thing is to use some OLAP software to use multidimensional analyze -
t
On 23/05/2012, at 17:20, Chris Ernst wrote:
> I would have a look at slony. It is a trigger based replication system
> that allows you to replicate only the tables you define and you can have
> different indexing on the slave. The only requirement is that each
> table you want to replicate has
On 05/23/2012 07:11 AM, Herouth Maoz wrote:
> Hi guys,
>
> I'm interested in a solution that will allow our customers to run reports -
> which may involve complicated queries - on data which is as up-to-date as
> possible.
>
> One thing I don't want to do is to let the reporting system connect
Hi guys,
I'm interested in a solution that will allow our customers to run reports -
which may involve complicated queries - on data which is as up-to-date as
possible.
One thing I don't want to do is to let the reporting system connect to the
production database. I want the indexes in product
