PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
N/A
Pragmatic Workbench (discontinued)
Score 8.5 out of 10
Enterprise companies (1,001+ employees)
Pragmatic Workbench Enterprise was a suite that combined four Pragmatic Works products: BI xPress, DBA xPress, DOC xPress and LegiTest. It was acquired by SentryOne in April 2018, and has reached its EOL phase. After the summer of 2022 it will likely no longer be available, and unsupported.
$2,490
per seat
Pricing
PostgreSQL
Pragmatic Workbench (discontinued)
Editions & Modules
No answers on this topic
Workbench Client Edition
2,490
per seat
Workbench Server Edition
8,995
per server
Workbench Enterprise Edition (Client + Server)
9,995
1 user / 1 server
Offerings
Pricing Offerings
PostgreSQL
Pragmatic Workbench (discontinued)
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Workbench Enterprise combines all of the functionality within Workbench Client (local install) and Workbench Server (server install).
More Pricing Information
Community Pulse
PostgreSQL
Pragmatic Workbench (discontinued)
Features
PostgreSQL
Pragmatic Workbench (discontinued)
Database Development
Comparison of Database Development features of Product A and Product B
PostgreSQL, unlike other databases, is user-friendly and uses an open-source database. Ideal for relational databases, they can be accessed when speed and efficiency are required. It enables high-availability and disaster recovery replication from instance to instance. PostgreSQL can store data in a JSON format, including hashes, keys, and values. Multi-platform compatibility is also a big selling point. We could, however, use all the DBMS’s cores. While it works well in fast environments, it can be problematic in slower ones or cause multiple master replication.
Workbench Enterprise is consistent across devices and users so far. It works the same, and access is easy. I have a problem with its security. If you use an enterprise password to access databases, it's very easy to click the show password on the connection page and expose the enterprise password. You shouldn't allow users to use the same accounts to access the database because that means all users are sharing the same password.
The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
Our team does the support for us. Sometimes we see download related issues that can easily be fixed by our team. Most issues you will see with one user in your org will probably happen to others, so keep a log and track those issues. Then have a fix for them somewhere that everyone has access to. This will save you a lot of time troubleshooting.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to MySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just as usable.
The user-role system has saved us tons of time and thus money. As I mentioned in the "Use Case" section, Postgres is not only used by engineering but also finance to measure how much to charge customers and customer support to debug customer issues. Sure, it's not easy for non-technical employees to psql in and view raw tables, but it has saved engineering hundreds of man-hours that would have had to be spent on building equivalent tools to serve finance or customer support.
It provides incredibly trustworthy storage for wherever customer data dumped in. In our 6 years of Postgres existence, we have not lost a byte of customer data due to Postgres messing up a transaction or during the multiple times the hard-drives failed (thanks to ACID compliance!).
This is less significant, but Postgres is also quite easy to manage (unless you are going above and beyond to squeeze out every last bit of performance). There's not much to configure, and the out of the box settings are quite sane. That has saved us engineers lots of time that would have gone into Postgres administration.