This article discusses some of Greenplum's best practices. Also, attached is the documentation for Greenplum Best Practices.
The definition of a best practice is a method or technique that has consistently shown results superior to those achieved by other means. Best practices are found through experience and are proven to reliably lead to the desired result.
Best practices are a commitment to use any product correctly and optimally, by leveraging all the knowledge and expertise available to ensure success.
Access the Greenplum Best Practices guide here. This guide is for Greenplum Version 4.3.
This document does not teach you how to use Greenplum features, please refer to the Greenplum documentation guides for information on how to use and implement specific features. Rather, this paper will address the most important best practices to follow when designing, implementing and using Greenplum.
It is not the intent of this document to cover the entire product or compendium of features but to provide a summary of what might be the best practices to adopt for a wholesome Greenplum experience.
This paper does not address edge use cases that can further leverage and benefit from these Greenplum features. Edge use cases require a proficient knowledge and expertise of these features and a deep understanding of your environment including SQL access, query execution, concurrency, workload and other factors. For such queries, refer to the Greenplum Knowledge Base.
By mastering these best practices you will increase the chances of success of Greenplum in the areas of maintenance, support, performance, and scalability.