You can translate the question and the replies:

Caching Service Views

There are 14 Service Views in my database which gives data from 2011 - 2018 (joining different combinedviews). We created partial service views for each of the service view by giving a where condition inside the Partial service view (less than 2016 and greater than 2016 for each) . When we are trying to cache on the partial service views layer (28 partial service views) using scheduler, it is looping through all the layers including baseviews, derivedviews, and combinedviews which is consuming a lot of time and creating a lot of swap files which is consuming a lot of harddisk space. Please advise me a best practice to run the caching on the partial service layer. Thanks and regards.
21-08-2017 15:05:30 -0400

1 Answer

Hi, For improving the caching, I would suggest you to add context clause parameter 'cache_return_query_results’=’false' into your cache lob job. This speeds up the process of inserting the data directly into the cache database because the result set from the query execution will not be returned to the client. As a result swap files will not be created thereby, helping you conserve more hard disk space. Have a look at the section "Avoid Obtaining the Result of a Query Executed to Load the Cache" in [Recommended Parameters for Queries that Load the Cache]( and [Cache Load Processes]( from Virtual DataPort Administration Guide. I hope this helps you!
Denodo Team
23-08-2017 08:29:10 -0400
You must sign in to add an answer. If you do not have an account, you can register here