Postgres Plus® White Papers and Data Sheets

White papers are below. Use the left hand navigation pane to click Data Sheets.

Postgres Overviews

While EnterpriseDB's Postgres Plus Advanced Server is built upon the rock-solid PostgreSQL foundation, it delivers many significant value-added features and add-on products not available in the community edition.

Research shows the typical DBA is responsible for an average of 35 databases with the trend only moving upward. Recognizing this issue, EnterpriseDB has introduced the first enterprise-architected management tool for DBAs who are looking to widely adopt Postgres in their enterprise and desire the same type of management capabilities they get from tools that are included from other database vendors that they work with. This whitepaper describes this solution – Postgres Enterprise Manager – in detail and focuses on how data management professionals will benefit from the enterprise-class capabilities supplied by the tool.

This white paper discusses many of the database-related pressures faced by IT managers today with regard to usage and costs. It reviews how every IT organization can find a class of applications for open source database adoption, and then use that experience to determine how wide and deep their open source database deployments can go to to fully benefit from consequent cost savings.

This paper examines four enterprise adoption strategies (and associated risk factors) for Postgres, and provides guidance to help readers develop an informed adoption playbook. The four strategies are analyzed for PROs and CONs across seven software adoption risk factors: Capabilities, Roadmap, Technical Support, Time To Market, Cost, Vendor Relationships and Software Control. The paper is written for all levels of IT management as well as for data architects, application development leaders and anyone involved in database strategy decisions. 

Postgres and Database Compatibility

Take a high-level tour through the five main areas of database compatibility built into Postgres Plus Advanced Server for Oracle® compatibility. For a more detailed document, download the Database Compatibility for Oracle Developer's Guide.

This guide describes the database compatibility features of Postgres Plus Advanced Server 9.4 for Oracle. It is the definitive reference for all the features that support Oracle databases and applications.

While many enterprises have been able to wring out significant cost savings by migrating to open source software for operating systems and middleware, there has been a reluctance to extend to the database layer due to concerns about complexity, risk and operational pain of migration. This paper will provide best practices for migrating Oracle applications to lower cost PostgreSQL alternatives; quantifying and mitigating associated risks; and reducing the operational pain associated with migration.

Although the most sensitive layer of the infrastructure stack, the database layer has the potential for the greatest cost savings and strategic advantages. For example, one Oracle license alone lists at $47,500 per processor core (without any add-on features) with annual operating expenses equal to 22% of the total license costs. Implementing Postgres is a wise alternative to Oracle’s business practices and price increases. Not only does this reduce capital and operating expenses, but IT vendor flexibility also increases.

Postgres Technical Topics

The use cases of replication can be many, however the core reasons that replication is used are the following: simple backup, sharded or read scale-out architecture, business intelligence / reporting, and simple high availability. This paper provides an overview of EnterpriseDB’s xDB Replication Server, describes how the solution functions, and then looks at the question of why the xDB Replication Server should be considered over the built-in replication functionality offered in PostgreSQL 9.0 and above.


This white paper demonstrates the benefit of EnterpriseDB Postgres Plus Advanced Server database on IBM Power Systems running Linux servers when compared to a similar configuration using the Intel Xeon processor-based system. 

Postgres and the Cloud

A recent study done by the IT industry analyst group IDC found that, while cloud computing accounts for less than 2% of IT spending today, it’s estimated that by 2015 nearly 20% of all information will be "touched" and enabled by cloud computing environments. IDC believes that as much as 10% of all data will be maintained in a cloud by 2015.

This equates to large volumes of data being stored in the cloud, with much of it being offered in a database-as-a-service (DBaaS) fashion. The data volumes stored in the cloud will likely be enormous, considering that IDC predicts a 50X data growth multiple in the next decade.

Modern businesses are looking to both public and private clouds as enablers for their database management systems. However, many admit that they struggle with selecting the database provider(s) to utilize in their move to cloud computing and what features they need in order to benefit from such a move. This paper examines the question of what constitutes an enterprise-class database that takes advantage of the various benefits of cloud computing environments.

Speed, agility and cost savings were the initial draw of cloud databases. Organizations are now looking to incorporate the cloud database into their infrastructures as they re-engineer their environments to support new development processes, operational models and data demands. The database, by many accounts, is poised for the strongest growth among public cloud computing product categories. Clearly, the question no longer centers on when or if organizations will adopt cloud databases, but how organizations will optimize their value and use them most effectively.

Healthcare businesses can now deploy their applications using Postgres Plus in the public cloud. The Health Insurance Portability and Accountability Act (HIPAA), the related Health Information Technology for Economic and Clinical Health Act (HITECH), and the HIPAA Final Omnibus Rule have laid out stringent requirements but make it possible for healthcare companies to move applications involving sensitive patient data to the cloud.

Postgres and MySQL

Postgres’ long-term support for and focus on server side programs (triggers and stored procedures), ACID compliance, data and referential integrity, and fine-grained access controls are much more mature and stable than MySQL, which only recently has started implementing some of these features. While not an exhaustive side-by-side comparison, this white paper outlines a few key differences between Postgres and MySQL and some of the benefits data professionals will find in working with Postgres.

Postgres and NoSQL

Most Postgres users don't need NoSQL. With new features and capabilities alongside several longstanding components and extensions, Postgres can support virtually all of today’s data types as well as unstructured and semi-structured data. This means Postgres can power many applications written for NoSQL technologies and developers can build applications in Postgres that achieve the same results as NoSQL solutions. 

This white paper explains some of the operational challenges presented by the use of NoSQL technologies, and how JSON and HStore in Postgres lets you build document databases and key-value stores within Postgres. 

This paper reviews and illustrates Postgres’ NoSQL capabilities in the context of Postgres’ robust relational competencies. The paper also describes performance tests that demonstrate that Postgres, the leading open source relational database solution, is a superior platform for handling most NoSQL workloads.

NoSQL-only solutions pose a host of challenges, complexities and even serious risks. Postgres Plus by EnterpriseDB solves this dilemma and enables you to combine unstructured data with relational tables, all while maintaining ACID compliance and centralized business processing rules and logic.

Postgres and SQL Server

Advances in technology and increased enterprise momentum have generated more and more queries from Oracle, DB2 and SQL Server users exploring PostgreSQL (also known simply as Postgres) for their database needs. Microsoft SQL Server users in particular have been very active in 2014, possibly due to recent changes in Microsoft pricing, or like so many others, have determined they are paying too much for their database. The nature and consistency of queries from SQL Server users suggest a fundamental misunderstanding of Postgres features and capabilities. This white paper seeks to clarify some of the most common misconceptions of PostgreSQL among SQL Server users.

Tell Us What You Think!

We want to improve this website, and we need your help! Please tell us how well this website meets your needs:

Begin Survey >>