24/7 Tanzu Greenplum Support with a 15-Minute Emergency SLA

Our Tanzu Greenplum support covers 24/7 emergency incident response with a 15-minute SLA, root cause analysis on every P1, query and plan tuning, distribution key and partition redesign, HA and backup verification, version upgrades, and Broadcom licensing support. Every ticket is handled by a named senior DBA assigned to your account. There is no tier-1 triage layer and no per-incident charge.

Broadcom's support handles vendor-side defects and patch escalations, and it is genuinely good at that. What it does not do is operate your cluster. AceMQ provides hands-on production DBA coverage — reading motion plans, rebuilding distribution keys, running gprecoverseg, sizing statement_mem for your workload. Most of our Greenplum customers run both in parallel, and because we are a Broadcom Expert Advantage Partner we can escalate into Tanzu engineering on your behalf when a problem really is a product bug.

P1 emergencies — segments down, master unreachable, warehouse unavailable — get a 15-minute first response with a senior DBA joining a live bridge. P2 critical issues are 1 hour, P3 high-priority 4 hours, and P4 standard questions next business day. These are contractual, not best-effort targets.

Usually, yes. Skew is a per-table property, not a cluster property, so the fix is redistributing the affected tables rather than rebuilding everything. We identify the skewed tables by row count per gp_segment_id, pick a distribution key with enough cardinality that also serves your dominant join pattern, and redistribute during a window. On very large fact tables this can take a day or more of elapsed time, which is why it is the longest resolution on our triage list — but it is nearly always cheaper than living with it.

Yes. We handle 5.x to 6.x and 6.x to 7.x upgrades with documented rolling procedures, pre-upgrade catalog checks, and a tested rollback plan. We also execute migrations onto Greenplum from Teradata, Oracle, Netezza, and Vertica, including SQL dialect translation and row-level validation before cutover.

Yes, and this is a common reason Tanzu customers call us. As Broadcom's VMware Expert Advantage Partner of the Year for the Americas, we reconcile deployed cluster capacity against purchased entitlements, flag true-up exposure before an audit finds it, and negotiate renewal and multi-year terms. Licensing quotes come back within 24 hours, and the engineers who size your cluster are the same team advising on what you actually need to license.

Greenplum Database is a massively parallel processing database system built on PostgreSQL, used for data warehousing and analytics across very large datasets: a coordinator plans each query and segments execute it in parallel. We support VMware Greenplum, now sold by Broadcom as Tanzu Greenplum, and the open-source Greenplum builds that lost their upstream when the project went closed source in 2024, on Greenplum database versions 5.x, 6.x and 7.x. Platforms covered are bare metal and virtual machines on Red Hat and other supported operating systems, vSphere, and public cloud deployments on AWS, Azure and GCP. Coverage includes the tooling around the database: PXF, the Platform Extension Framework used to query external data sources, gpbackup and gprestore, JDBC and ODBC connectivity for BI tools, and the gpsupport utility for collecting log files when a case needs escalating to Broadcom.

Most calls are about a Greenplum database cluster that is slow rather than down. We check segment and mirror health first, then free space and log files, then the query: distribution keys that skew data across segments, missing statistics, resource queues or resource groups that starve concurrent work, spill files from queries that exceed their memory, and catalog bloat that slows every operation. Configuration reviews cover the operating system settings Greenplum depends on, connection pooling, and compatibility between the Greenplum version, the client drivers and the ETL tools that load it. The aim is to leave the cluster with documented settings and a runbook, so the next incident is shorter.

Yes. AceMQ works on Greenplum in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.

Every AceMQ proposal is tailored to your requirements: your Greenplum environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Greenplum is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.