Idea ID: 1762700

Add historical querys - second DB connection

Status : Waiting for Votes
over 2 years ago

Is there any chance to connect a just read-only database so we are able to read historical data from the same OO installation? In our bank there are a lot of applications which have the option to dump historical data to a second DB and read the data from it within the same interface (we have got the obligation of backing up data for 10 years and a single OO DB which is growing faster it's not good for performance).

I just hope that I won't be the only one with this issue :)

Best regards, Alexis.

  • Florin, thanks. I forgot this thread, I had opened an ER via case manager but I've been noticed that this is the proper way now.

    Alexis, can you provide a clear use case on how you would see such a functionality, how it should work?

    An ideal situation would be have on the run management menu an option like "run explorer" but pointing to a historical database, keeping the records. The merge mechanism between tables has to be implemented with a sp, for example

    How do you expect to guarentee the data intergrity in an environment that doesn't support downtime?

    Here we have a problem, so we have to establish some kind of "maintenance window mechanism" in order to do the data replication.

    If a downtime for data replication is acceptable in your environment, what is the maximum downtime possible and at what intervals (days, weeks, monthly)?

    Really in our case we have such a little possible maintenance period, 30 min at work days, maybe we could have more time at weekends. The daily backup routine of the DB may be helpful?

    As a workaround we tried to install another central instance and identified some tabled with the information needed but we haven't got all the description and we can't restore the entire database because we are duplicating the scheduled executions, having two productive instances with multiple access.

    Thanks for all your assistance.

  • Alexis, can you provide a clear use case on how you would see such a functionality, how it should work?

    How do you expect to guarentee the data intergrity in an environment that doesn't support downtime?

    If a downtime for data replication is acceptable in your environment, what is the maximum downtime possible and at what intervals (days, weeks, monthly)?

    Setting status to Waiting for Votes to get community feedback.

    Thanks,
    Florin