WarehousePG - Binary Swap

Service Overview

The EDB WarehousePG Binary Swap service is designed to facilitate a smooth and efficient transition for customers moving from their existing Greenplum Distribution to a fully supported and optimized version of EDB WarehousePG. This engagement is a crucial step in ensuring continuity, enhanced performance, and access to EDB's robust support ecosystem. 

(Reference the Sizing document for the detailed questions outlining the tier determination.)

Scope of Service

Our Consultant will validate the prerequisites, configure and deploy the WarehousePG cluster, and validate Standard Operating Procedures (SOPs) for the agreed architecture, replacing the existing Greenplum environment:

Discovery and Planning

• Document the current Greenplum environment, including version, configuration, and dependencies.
• Define the target configuration for the new WarehousePG environment.
• Run an assessment script to collect all the required information useful for the binary swap: this assessment has to be executed on all clusters (including production)
• Identify which WarehousePG must be installed
• Identify the possible impacts or changes that should be made before the swap.
• Perform the changes identified above

• Secure necessary approvals and resources for the binary swap project.

   

Testing and Validation

• Document and execute the binary swap in a single non-production environment.
• Perform quality checks and validate the functionality of the new WarehousePG architecture.
• Review and refine Standard Operating Procedures (SOPs) based on the test results.
• Provide a demonstration of the new WarehousePG architecture and confirm knowledge transfer.
• Perform a test of binary swap and a rollback in order to verify that we can easily go back on Greenplum

Execution and Verification

• Perform the binary swap deployment in the production environment.
• Verify the successful migration and operational readiness of the new WarehousePG system.

Deliverables

• Binary swap completed and operational in one (1) non-production environment and one (1) production environment  WarehousePG Cluster
• Runbook
• Performance baseline report 
• Operational handover docs

Roles and Responsibilities

EDB Project Manager:  Responsible for initial planning, task alignment, and project closeout.

EDB Senior Consultant: Technical Lead, responsible for prerequisite validation, config and deployment, SOP Validation and documentation.

Customer Team: Responsible for providing the main point of contact for design requirements. Resources and Roles (or similar Technical Stakeholders) where input may be needed for the engagement include:

• Database Administrator
• System Architect
• Infrastructure Manager 
• Network Administrator
• Security Officer

Assumptions

• A project kickoff will be conducted to review the service scope and confirm the schedule
• This service is delivered remotely unless otherwise agreed
• EDB will deploy the architecture with the EDB-supported version of WarehousePG.
• Deployment is validated in a non-production environment (no live traffic) before Production execution. 
• Customer environment is not air-gapped (unless "Air Gapped Repo Setup" is purchased separately)
• Performance testing, outside of initial benchmark, and application readiness are not in scope.
• EDB will measure baseline performance (based on gpcheckperf and TPC-DS)
• Customer will provide the names, title, email, phone number, and area of responsibility of those participating. One person will be designated as the main contact, and will be able to provide access to the people most knowledgeable about the topics to be discussed or examined. 
• Customer will make appropriate personnel available to assist EDB in the performance of the services as needed and requested by EDB in a timely manner so as not to disrupt the project schedule. 
• Customer will not provide Personal Data (as defined in applicable law). Customer agrees that it will work with EnterpriseDB to ensure that all such data is not provided.  
• Customer will ensure timely access to all systems through screen sharing and experts including third parties as required. 
• Customer will assign the appropriate resources with the appropriate privileges for the task being planned for any screen sharing sessions as needed throughout the engagement.
• Customer will provide timely feedback on all deliverables. Deliverables without commentary within 5 business days will be deemed as delivered.
• The Customer is responsible for configuring application-side connection strings, Virtual IPs (VIPs), or external Load Balancers to route traffic to the active Primary node or, when "Connection Pooling" is explicitly included in the tier, to the active connection pooler instance.
• The Customer provides the list of queries that will be used to compare the performance before and after the binary swap
• If the Customer wants to check the performance before and after the swap for reports and/or loading jobs executed on third party-tools, the Customer runs the reports and/or loading jobs before and after the swap

Prerequisites

• Customer will provide resource availability for workshop planning and a point of contact for coordination. 
• Server prerequisites will be prepared by the customer team before the kickoff of the project.
• Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, operate, or modify customer implemented systems.
• Customer security team has approved all required software packages.

Standard Operating Procedures

EDB will validate the below test cases as part of the validation process:

Sizing

EDB offers the Binary Swap of WarehousePG in Small, Medium, and Large tiers, to fit a variety of requirements. Please answer the following questions and provide to your designated Account contact for appropriate pricing.