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
Presto
Score 2.9 out of 10
N/A
Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
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.
Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica
Linking, embedding links and adding images is easy enough.
Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
Organizing & design is fairly simple with click & drag parameters.
Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.
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.
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.
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.
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
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.
