The Oracle Database, now in edition 19c, is presented by the vendor as an industry leading database that delivers leading-edge innovations, including machine learning to enable self-driving data management. An enterprise, database cloud service, it is designed to support mixed workloads through any deployment strategy, on premises or in the cloud.
N/A
SingleStore
Score 9.3 out of 10
N/A
SingleStore aims to deliver the world’s fastest distributed SQL database for data-intensive applications: SingleStoreDB, which combines transactional + analytical workloads in a single platform.
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.
Our workload is 100% analytical. We also have to ingest a lot of data each month. SingleStore is a perfect match for our needs because it has fast pipelines for data ingestion and great performance, even in large and complex queries. We need fast response times for our user interface and great performance in our ETL processes, which are rather complicated. SingleStore handles all of this very well.
We wish the product had better support for High Availability of the aggregator. Currently the indexes generated by the two different aggregators are not in the same sequential space and so our apps have more burden to deal with HA.
More tools for debugging issues such as high memory usage would be good.
The price was the one that kept us away from purchasing for the first few years. Now we are able to afford due to a promotion that gives it at 25% of the list price. Not sure if we'll continue after the promotion offer expires in another 2 years.
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.
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
SingleSore can perform transactions and operational analytics together in order to utilize their data and transform their business. SingleStore delivers a database that performs both functions. Before using SingleStore, we had different systems for OLTP queries and for OLAP analyses, and a number of ETL packages to bring data from the OLTP system to Reporting database.
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.
Very responsive to trouble tickets - Often, I think, the SingleStore's monitoring systems have already alerted the engineers by the time I get around to writing a ticket (about 10 - 20 mins after we see a problem). I feel like things are escalated nicely and SingleStore takes resolving trouble tickets seriously. Also SingleStore follows up after incidents to with a post mortem and actionable takaways to improve the product. Very satisfied here.
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
We allowed 2-3 months for a thorough evaluation. We saw pretty quickly that we were likely to pick SingleStore, so we ported some of our stored procedures to SingleStore in order to take a deeper look. Two SingleStore people worked closely with us to ensure that we did not have any blocking problems. It all went remarkably smoothly.
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.
Vertica, Snowflake, SQL Server, Azure Data Warehouse, PowerBI, Aerospike, etc. From what I've seen MemSQL is well worth the cost when latency and data freshness needs are high, i.e. you need a lot of queries to run with UI latency (the query itself takes less than a second or so), with very fresh streaming fact and dimensional data. It will be more expensive per "unit of performance" but if you need that performance then it'll get the job done.
On-prem Vertica (note, not Eon) provides more knobs for optimizing a particular data set and set of queries against it and performs as well or better in a single table, fact table queries. It will also scale to data size more cheaply due to its on-disk model. For large queries against large data sets where data freshness isn't as important (and latency either is or isn't), I'd take Vertica, although if you need to do a lot of joins that will struggle). However, as they still are exclusively columnar, dimension table updates, and recalls based on them, can only be tuned to happen so fast (we could do much better than 10 seconds with 10-100 updates per second for raw replication, and Vertica's joins are always slow so recalls were worse).
Snowflake suffers similarly to Vertica in the data freshness, replication, and re-calc area; SF also doesn't give as many knobs to turn as Vertica for data set optimization but seems to be better at joins. If you have a lot of queries to run against a lot of data and joins are limited, you need query latency low and consistent but you don't need a ton of freshness, I'd stick with Vertica. If joins matter more, or you can accept notably-but-not-terribly worse performance, then Snowflake is fine and cheaper from what we've seen. (Again, I can't speak to SF vs Vertica Eon).
SQL Server and ADW we couldn't get to perform as well as the other options, but I'll say we didn't try that hard on those.
Aerospike is amazing as a KV store; however for OLAP use cases where you want to balance performance against the flexibility of queries against general event (time series) data (i.e. be able to roll up to different grains) then KV becomes challenging.
PBI is great if you want an integrated BI tool, but if you want an OLAP solution to build against, with some particular scale or performance needs to be mentioned above, I'd go with one of these other solutions. It really can be great for letting non-tech folks build relatively small data sets and quick insights for customers (internal or external), great leverage in that case.
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.
As the overall performance and functionality were expanded, we are able to deliver our data much faster than before, which increases the demand for data.
Metadata is available in the platform by default, like metadata on the pipelines. Also, the information schema has lots of metadata, making it easy to load our assets to the data catalog.
