Oracle Database, currently in edition 23c, offers native support for property graph data structures and graph queries. If you're looking for flexibility to build graphs in conjunction with transactional data, JSON, Spatial, and other data types, we got you covered. Developers can now easily build graph applications with SQL using existing SQL development tools and frameworks.
N/A
PostgreSQL
Score 8.5 out of 10
N/A
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.
We have used Microsoft SQL Server for some smaller projects where the vendor only supports that environment. But whenever there is a choice, we use Oracle Database 12c. Students access our systems at all …
Even if is quite expensive, Oracle Database 12c is way better than most of its competitors thanks to Oracle experience and skills on database technologies. Oracle Database has always guaranteed the best data recovery and fault management policies, thanks to Oracle's RAC …
Not at my current employer, but previously I have evaluated and used all Microsoft SQL Server, Amazon Web Services (AWS), PostgreSQL and MySQL. All of them had their own advantages and disadvantages. SQL Server had great built in tools like SSIS and SSRS that integrated well …
Oracle Database is best in business, consistent, and robust. Even the standard version is sufficient for the best performance. The main thing is I have never seen corruption and in my opinion, it is best when used with Linux.
Verified User
Administrator
Chose Oracle Database
In my opinion, Oracle Database is highly reliable, has better performance with large databases and little to no maintenance once everything is setup. Also, recovery of the Oracle database is much simpler and easier.
Oracle Database is among the easiest to integrate with, program against, have a reliable cluster with DR, and has the most understood and well-documented databases. It suits really well if the software shop is primarily Java-based, and deals with large volumes of data with a …
Oracle is serving a different segment with respect to those above. Till now, we have stuck with Oracle and continued to support our internal customers. Other DBs are serving a few targeted applications by a few application teams.
Oracle completed solution and support is of cause better than open source solutions, we also choose other NoSQL database and Graph database, to address some very particular business use cases
it was not my choice for Oracle 12C, but during the years I've learned on the advantages. If I would choose the Oracle 12C, I'll take it for the possibility to start from Standard and to go to enterprise based on a business case of use. I really like the possibility to have the …
We're still in evaluation but based on cost and affordability vs. performance for our specific needs (running a $500M retail e-commerce shop) Oracle 12c loses. Licensing and support of Enterprise Edition would equate to a significant percentage of our annual revenue and we …
Well, Oracle is a solid database and as I mentioned, is for the first quartile of project complexity. The other solutions mentioned databases have more specific goals and respond to reduced complexity. For example MySQL or PostgreSQL are widely used for startups. On the other …
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
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 …
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets. We are Linux based solutions and …
PostgreSQL is the proper tool when data consistency matters and other BASE or document-based databases are simply improper. I think PostgreSQL has a fantastic system of slony replication, triggers, and other data maintenance functionality that other databases generally don't …
I believe Oracle Database is still the best RDBMS database which is the database to consider for OLTP applications and for Adhoc requests. They are good in Datawarehousing in certain aspects but not the best. Oracle is also a great database for scaling up with their Clusterware solution which also makes the database highly available with services moving to the live instance without much trouble.
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.
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.
There is a lot of sunk cost in a product like Oracle 12c. It is doing a great job, it would not provide us much benefit to switch to another product even if it did the same thing due to the work involved in making such a switch. It would not be cost effective.
Many of the powerful options can be auto-configured but there are still many things to take into account at the moment of installing and configuring an Oracle Database, compared with SQL Server or other databases. At the same time, that extra complexity allows for detailed configuration and guarantees performance, scalability, availability and security.
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.
1. I have very good experience with Oracle Database support team. Oracle support team has pool of talented Oracle Analyst resources in different regions. To name a few regions - EMEA, Asia, USA(EST, MST, PST), Australia. Their support staffs are very supportive, well trained, and customer focused. Whenever I open Oracle Sev1 SR(service request), I always get prompt update on my case timely. 2. Oracle has zoom call and chat session option linked to Oracle SR. Whenever you are in Oracle portal - you can chat with the Oracle Analyst who is working on your case. You can request for Oracle zoom call thru which you can share the your problem server screen in no time. This is very nice as it saves lot of time and energy in case you have to follow up with oracle support for your case. 3.Oracle has excellent knowledge base in which all the customer databases critical problems and their solutions are well documented. It is very easy to follow without consulting to support team at first.
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.
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.
Overall the implementation went very well and after that everything came out as expected - in terms of performance and scalability. People should always install and upgrade a stable version for production with the latest patch set updates, test properly as much as possible, and should have a backup plan if anything unexpected happens
Oracle is more of an enterprise-level database than Access and SAP Adaptive Server Enterprise isn't getting developed much (some people wonder how close it is to end of life) but SQL Server is miles ahead of Oracle IMO in terms of user experience and comparable in terms of performance AFAIK. As stated, a vendor forced our hand to use Oracle so we did not have a choice. If you are looking for help with an issue you are having, there are lots of SQL Server articles, etc. on the web and the community of SQL Server developers and DBA's is very strong and supportive. Oracle's help on the web is much more limited and often has an attitude that goes with it of superiority and lacking in compassion, IMO. For instance, check out the Ask Tom Oracle blog - a world of difference. If you choose Oracle, go into it with eyes wide open.
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.
Oracle Database 12c has had a very positive impact on our ability to build strong and robust custom applications in house without the need to come up with our own methods of data storage and management.
Oracle Database 12c has the strongest user interface of any database I have worked with and continuously is improving its strength with the addition of support for JSON and XML type objects in the database.
Oracle Database 12c is sometimes very heavy and DBA intensive, but the benefits far outweigh the costs, which we need to spend on DBA support for enabling security and access features.
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.
