Please note: Pentaho's offices will be closed Monday May 29th in observance of Memorial Day as we honor and celebrate our Veterans.
Because of this, you may notice a small delay in response from Pentaho. Thanks for understanding, and Happy Memorial Day!

Best Practices - Dividing Large PDI Repositories

Your feedback is important to us!  Email us how we can improve these documents.

Software Versions
Pentaho   6.x, 7.x

Overview

Many customers initially create a single Pentaho Data Integration (PDI) repository to maintain multiple environments – e.g., development, quality assurance, stage, production – when first installing PDI. These customers then divide this single repository into different environments using nested folders.

Over time, this single repository may grow to a size that negatively impacts performance. Customers may also find that management of a single repository is cumbersome, even if all environments are non-production. This document addresses these problems by detailing an automated method to improve performance by segmenting a single repository into several smaller repositories using PDI.

   -  Best Practices - Dividing Large PDI Repositories

Have more questions? Submit a request

Comments

Powered by Zendesk