Re: Sort-of replication for reporting purposes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I suggest SymmetricDS.  ( http://symmetricds.org )

I've had good luck using them to aggregate data from a heterogeneous suite of database systems and versions back to a single back-end data mart for exactly this purpose.



On Fri, Jan 6, 2017 at 2:24 PM, Ivan Voras <ivoras@xxxxxxxxx> wrote:
Hello,

I'm investigating options for an environment which has about a dozen servers and several dozen databases on each, and they occasionally need to run huge reports which slow down other services. This is of course "legacy code". After some discussion, the idea is to offload these reports to separate servers - and that would be fairly straightforward if not for the fact that the report code creates temp tables which are not allowed on read-only hot standby replicas.

So, the next best thing would be to fiddle with the storage system and make lightweight snapshots of live database clusters (their storage volumes) and mount them on the reporting servers when needed for the reports. This is a bit messy :-)

I'm basically fishing for ideas. Are there any other options available which would offer fast replication-like behaviour ?

If not, what practices would minimise problems with the storage snapshots idea? Any filesystem options?



[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux