You can translate the question and the replies:

Derby DB meta data

We are currently working on upgrading performance validation and upgrading to DENODO 8. While working on noticed Meta data configurations are set to default ehich is initial 4 and max 100.Lookking for way to update these to higher number to support our concurrent end user need as it could be adding response time for our on demand view invoke. I see very less ocumentation related to how and when process would connect to derby db and how long it is taking. Much appriciated if could share more details and set these parameters like other connections. Thanks in advance.
user
08-06-2022 14:19:37 -0400
code

1 Answer

Hi, The default metadata storage using the internal Derby database gets managed by the VDP server itself and property values are not exposed to be modified. Although, if required, I would store the metadata in an external database which can be managed by the respective DBAs. The documentation at [Storing the Metadata on an External Database](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/server_configuration/storing_catalog_on_external_database/storing_catalog_on_external_database#considerations-about-this-feature) details the procedures and recommendations around this setup. Also, VDP server provides configurations to manage concurrent queries. The reference material can be found at [Limiting the Number of Concurrent Requests](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/server_configuration/limiting_the_number_of_concurrent_requests/limiting_the_number_of_concurrent_requests). Hope this helps.
Denodo Team
10-06-2022 08:39:47 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here