How intrusive is the DV at the time of a consultation?

[cristopher.torres]

Hello we want to see if the DV is intrusive with the source databases at the moment of making constant queries.

[rareddy]

Constant queries? can you expand the question further?

Source is only consulted when needed based on the user query submitted.

[cristopher.torres]

We have a database in which is all the information of the customers, this database provides information for many sectors of the company. Currently a new system of consultations has been added, but in order not to have much impact on the database with each consultation, a mechanism has been established to extract information from it once a day at night, thus having an information gap Of 24 hrs.

The DV allows us to see the data in real time. However, we wanted to know how much it would impact the data manager for the queries made in this.

[rareddy]

Where is consulted information stored for 24 hrs? if this in a separate database, then if you use this database in DV then the original database is never consulted. If your DV is reading from original database, then you need to use "materialization" feature where you can save the customer information for 24 hrs, then DV will consult once in 24 hours.

See materialization here. 3.7. Internal Materialization - Red Hat Customer Portal  and there is also external materialization 3.2. Use External Materialization - Red Hat Customer Portal 

[cristopher.torres]

Yes, we use a separate base that we no longer want to use to make the point-to-point connection with the DV.

Then in this case there is no way to view the data in real time without this impact to the source database?

[rareddy]

Not without querying the original database. If you want data in real time that is the only way.

[cristopher.torres]

Okay, thanks for clearing up my doubts