Overview
ProductRatingMost Used ByProduct SummaryStarting Price
SingleStore
Score 7.5 out of 10
N/A
SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.
$0.69
per hour
Azure SQL Database
Score 8.9 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
$0.50
Per Hour
Pricing
SingleStoreAzure SQL Database
Editions & Modules
OnDemand
$0.69
per hour
2 vCORE
$0.5044
Per Hour
6 vCORE
$1.5131
Per Hour
10 vCORE
$2.52
Per Hour
Offerings
Pricing Offerings
SingleStoreAzure SQL Database
Free Trial
YesNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeOptionalNo setup fee
Additional Details
More Pricing Information
Community Pulse
SingleStoreAzure SQL Database
Considered Both Products
SingleStore
Chose SingleStore
I can only compare it with Exasol, which I have used a similar base, which manages the Hadoop scheme and is very similar to SingleStore. SingleStore has many advantages: being in the cloud, with just a couple of clicks I can increase the capacity, the configuration is super …
Chose SingleStore
first of all SingleStoreis a cluster with high availability and easy to use.
you need to design you tables / procedures such in a way that your SingleStore perform well and with handle heavy load
Chose SingleStore
Reduces database sprawl, ETL costs, infrastructure expenses, etc. Supports horizontal scaling, unlike PostgreSQL & Aurora, and real-time analytics and fast transactions (HTAP), unlike Snowflake & ClickHouse.Handles high-volume workloads with thousands of concurrent queries. No …
Chose SingleStore
SingleStore (memsql) out performs based on our analysis with sample data sets within org. We could see limitations with other products which SingleStore can overcall like scaling with data while performing with similar SLA. It also has the advantage of row store and column …
Chose SingleStore
Efficient and faster data ingestion was primary criteria.
Chose SingleStore
SingleStore outperforms Snowflake in real-time analytics and transactional workloads but lags in large-scale batch processing. Compared to MongoDB Atlas, SingleStore excels in complex SQL queries and joins, while MongoDB handles unstructured, document-based data better. Its …
Chose SingleStore
Greenplum is good in handling very large amount of data. Concurrency in Greenplum was a major problem. Features available in SingleStore like Pipelines and in memory features are not available in Greenplum.

Gemfire was not scaling well like SingleStore. Support of both …
Chose SingleStore
We previously used Bigquery for our application, and a single store gave us very good performance over Bigquery. But the comparison is not apples to apples, as Bigquery is more of a data warehousing solution.
Chose SingleStore
SingleStore is just a bigger engine with more capability. Its ability to handle larger data sets with ease is its biggest advantage. These other database solutions are great for smaller scale projects that don't include large data sets but Singlestore greatly out performs in …
Chose SingleStore
DynamoDB was fast but no ability to do OLAP queries

Aurora couldn't handle our data scale at all
Chose SingleStore
It has more APIs and other access methods. It has a multi-version concurrency control (MVCC) Distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in …
Chose SingleStore
Its easier to query and faster. Ingestion is for the most part easier to understand and monitor and directly integrated with other storage solution products we use such as AWS S3. Singlestore overall is a better database to serve up an application large amounts of data very …
Chose SingleStore
ClickHouse - would still require us to have a separate db.
ElasticSearch - seemed too complex for us.
Chose SingleStore
SingleStore provided the best performance for our need to slice and dice for a large columnar dataset.
Chose SingleStore
SingleStore is built for fast data ingestion and fast queries against large tables (> billions of rows). This is possible because of the column store engine that SingleStore uses. SingleStore also support a memory engine. Pipelines is also another big advantage. Being able to …
Chose SingleStore
SingleStore has outperformed these in speed and performance. However it is more expensive but has been worth the cost so far.
Chose SingleStore
We knew early on that MySQL (Amazon Aurora) would not be suitable for this workload as it cannot query our time series data as fast as SingleStore. We also use MongoDB Atlas for another application but we could not achieve the raw speed we saw from SingleStore. Our technical …
Chose SingleStore
We were initially using AWS Aurora which worked well at the time but as we grew it just felt like a lumbering beast - even with tier upgrades. We started looking at caching & search options to help make searches faster - we were already using redis. We looked at and even …
Chose SingleStore
Timescale was the biggest alternative option we looked at for SingleStore, however the requirement to learn a new syntax (due to not being SQL compatible) was our biggest pain point.

Supporting a new language would require alterations to the Laravel framework, as this only …
Chose SingleStore
SingleStore provides an abstraction layer in managing a sharded database solution reducing complexity for the FLOWD team. Coupled with the SingleStore Managed Service, we are partnering with SingleStore to provide FLOWD services to various utilities & councils.
Chose SingleStore
SingleStore is eons faster than other database providers, and it absolutely crushes calculations & aggregations. While other providers may have a few quality of life enhancements over SingleStore, the speed benefits of SS far outweigh the cons. At the end of the day, speed …
Chose SingleStore
SingleStore provides performance for real-time data analytics application where as Snowflake is more for data engineers and not fast enough for real-time data analytics apps.
Chose SingleStore
As I said before, we felt that running queries on BigQuery for every query is really slow, especially from an user point of view. After seeing the drastically improved latency of SingleStore we decided to use to solve this issue. We currently use it to run low volume queries …
Chose SingleStore
SingleStore was the fastest sql database we have tried, allowing for analytical queries on TBs of data.
Azure SQL Database
Chose Azure SQL Database
We have selected it because we are using Azure Cloud and it is the best option for us to go ahead with Azure SQL Database.
Chose Azure SQL Database
The simplicity and great features and good support of Microsoft as well as the more reasonable flexible price than other competitors is one of the important reasons for choosing it.
Chose Azure SQL Database
Oracle database is "the" serious database. There really is no competition in that field. SQL Database would be a serious competitor through the ease of implementation and the "no maintenance," but since it's too expensive for "normal" use (medium to small applications), it just …
Chose Azure SQL Database
We looked at Google Cloud SQL and Amazon RDS services, but we did not want to switch to a different structure from the system we currently use.
Chose Azure SQL Database
It is very easy to setup SQL database on Azure. one can always refer to their documentation for best practices. It is highly available and scalable. It is cheaper than its alternatives and provide better performance than others. As we are using many other services of Azure for …
Chose Azure SQL Database
Amazon RDS for SQL Server is the best example to compare with Azure SQL Database since both provide a Microsoft SQL Engine to host your databases.

Amazon RDS for SQL is much more compatible with your on-premises databases than Azure SQL, the reason is that Amazon RDS for SQL …
Chose Azure SQL Database
The Azure SQL Database, compared to our on premise SQL server installation, is much easier to use in terms of seeing database diagnostics. There is a whole visualization platform that comes with the tool that will allow your database administrator to see what jobs are tying up …
Chose Azure SQL Database
Amazon's RDS offering is actually very good and is used in other parts of the company, we just have a lot of Azure experience so wanted to leverage that.
Chose Azure SQL Database
Azure SQL has a slight advantage over its rivals because it's developed by Microsoft, so it is well suited to professionals.
Chose Azure SQL Database
Being able to manage our databases in the cloud, scale quickly, and only require access to VMs made choosing Azure a no-brainer over a traditional SQL Server installation/integration. We don't have the budget or resources to integrate and maintain servers on our own, so using …
Chose Azure SQL Database
I would say MySQL in either Aurora or MariaDB form come close however, Azure SQL Database has a more streamlined approach to delivering a consistent programmability model, supported drivers and feature set.
Azure SQL Database T-SQL is advantageous and more complete than SQL …
Chose Azure SQL Database
Azure owned by Microsoft who owned SQL Server, so provided a variety of tools for easy migration/transition and from on-premises to the cloud; and management. I recommend using Azure for any on-prem SQL server databases.
Chose Azure SQL Database
Very similar product. Our company preferred to remain in the Microsoft Software Suite.
Chose Azure SQL Database
Azure SQL is a clear upgrade to SQL Server 2012 and pretty much has the advantage with all the extra features that it has. Security, queries, exporting tables, T-SQL has all improved. Transitioning 18+ years of an in-house database to the cloud was a struggle, but for the …
Chose Azure SQL Database
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure …
Chose Azure SQL Database
Amazon Relational Database Service is the other obvious competitor. We were already in Azure, so it's not a serious contender for our business due to that bias already, but I do personally find the marketing and documentation of RDS more intimidating to sort through.
Chose Azure SQL Database
Comparing with Amazon Aurora: Azure SQL DB is 100% compatible with SQL Server and Aurora is compatible with MySQL and PostGreSQL. Because of if, SQL DB suits large enterprises with hundreds of databases better.
Comparing with Oracle: the main issue is that Oracle will try to …
Chose Azure SQL Database
It reduces the business cost as it provides large storage capacity with massive speed. Data security is primary benefit which this product gives me.
Chose Azure SQL Database
It stacks up in different ways, for the most part, I think Microsoft is doing a really good job versus the competition. They basically started database type products from the beginning. I've always been excited about updates and can see their progress over time. Get's me really …
Chose Azure SQL Database
AWS's solution would be an alternative. I felt since we're a Window shop and already had a small investment into Azure, it was a no brainer.
Chose Azure SQL Database
It's more easy to shift and get all the services up in no time, provide best up time and monitoring easily so you can get the best services which take care of themselves. It's a better fitting for a large company size.
Chose Azure SQL Database
If you are a company that is already invested in Microsoft technologies, then the Azure suite is a better fit than the Amazon suite.
Chose Azure SQL Database
As we were early adopters with Azure and landed on the Azure PaaS (Platform as a Service), it made sense to use databases that were on the same platform as the application to save on costs. Also, we were impressed with the simplicity of Azure SQL. From a management perspective …
Features
SingleStoreAzure SQL Database
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
SingleStore
-
Ratings
Azure SQL Database
9.2
Ratings
6% above category average
Automatic software patching00 Ratings9.00 Ratings
Database scalability00 Ratings9.00 Ratings
Automated backups00 Ratings10.00 Ratings
Database security provisions00 Ratings9.00 Ratings
Monitoring and metrics00 Ratings8.00 Ratings
Automatic host deployment00 Ratings10.00 Ratings
Best Alternatives
SingleStoreAzure SQL Database
Small Businesses
InterSystems IRIS
InterSystems IRIS
Score 7.7 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Medium-sized Companies
InterSystems IRIS
InterSystems IRIS
Score 7.7 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Enterprises
SAP IQ
SAP IQ
Score 10.0 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
SingleStoreAzure SQL Database
Likelihood to Recommend
7.6
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
8.2
(0 ratings)
8.0
(0 ratings)
Usability
8.2
(0 ratings)
9.0
(0 ratings)
Availability
9.1
(0 ratings)
-
(0 ratings)
Performance
8.2
(0 ratings)
-
(0 ratings)
Support Rating
8.3
(0 ratings)
9.0
(0 ratings)
Online Training
7.3
(0 ratings)
-
(0 ratings)
Implementation Rating
7.3
(0 ratings)
-
(0 ratings)
Ease of integration
9.1
(0 ratings)
-
(0 ratings)
Product Scalability
8.2
(0 ratings)
-
(0 ratings)
Vendor post-sale
8.2
(0 ratings)
-
(0 ratings)
Vendor pre-sale
8.2
(0 ratings)
-
(0 ratings)
User Testimonials
SingleStoreAzure SQL Database
Likelihood to Recommend
Well-Suited Scenarios: Real-Time Analytics: Financial trading platforms requiring instant insights. Operational Dashboards: Retail businesses monitoring live sales. IoT Data Processing: Smart device monitoring with high data ingestion. Fraud Detection: Banks detect suspicious transactions instantly. Less Appropriate Scenarios: Archival Storage: Cold data storage with infrequent access. Low-Volume Workloads: Small-scale apps with minimal data processing needs. Complex ETL Pipelines: Heavy data transformations without real-time demands.
Read full review
Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.
Read full review
Pros
  • Return results of complex queries scanning TBs of data in sub-seconds.
  • Customer support team answer tickets quickly and provide guidance.
  • MySQL engine which allows to query using simple MySQL drivers from different clients.
  • Queries profiling is easy to use and helps investigating performance.
Read full review
  • Scalability is #1: if it used to be an almost no-win endeavour to try to modernize your server or migrate to other hardware, with Azure SQL Database it becomes a press of a button.
  • All the tools simply work after you are on Azure SQL Database.
  • The applications do not need changes in order to start using Azure SQL Database.
  • Hybrid Cloud scenarios will work.
  • Clustering and failover - already there.
  • You can start monitoring the use and extract performance insights in a new way in Azure.
Read full review
Cons
  • It does not release a patch to have back porting; it just releases a new version and stops support; it's difficult to keep up to that pace.
  • Support engineers lack expertise, but they seem to be improving organically.
  • Lacks enterprise CDC capability: Change data capture (CDC) is a process that tracks and records changes made to data in a database and then delivers those changes to other systems in real time.
  • For enterprise-level backup & restore capability, we had to implement our model via Velero snapshot backup.
Read full review
  • A little slow on processing complex or large Views. We use a lot of Views to feed our BI system, and the processing time could see some improvement, IMHO.
  • Additional monitoring components would be nice too, automating some built in performance measurement tools would be a nice feature.
  • Price can always be improved as well. It’s not bad, but room for improvement.
Read full review
Likelihood to Renew
We haven't seen a faster relation database. Period. Which is why we are super happy customers and will for sure renew our license.
Read full review
This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.
Read full review
Usability
[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.
Read full review
It just works!
Read full review
Reliability and Availability
I really can't remember a time when it was not available
Read full review
No answers on this topic
Performance
When it comes to ingestion speed, SingleStore is probably at the top. Being able to create pipelines using SQL to ingest data from S3, Kafka, and other sources, is a great advantages. This means you can dynamically ingest data by customizing your SQL queries. SingleStore pipelines are pretty sophisticated, yet very simple. Few lines of codes and you are ingesting data, while still able to perform analytical queries on your billions of row tables.
Read full review
No answers on this topic
Support Rating
The support deep dives into our most complexed queries and bizarre issues that sometimes only we get comparing to other clients. Our special workload (thousands of Kafka pipelines + high concurrency of queries). The response match to the priority of the request, P1 gets immediate return call. Missing features are treated, they become a client request and being added to the roadmap after internal consideration on all client needs and priority. Bugs are patched quite fast, depends on the impact and feasible temporary workarounds. There is no issue that we haven't got a proper answer, resolution or reasoning
Read full review
We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.
Read full review
Online Training
Would prefer in person training but for online training, it's almost as good as in person
Read full review
No answers on this topic
Implementation Rating
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.
Read full review
No answers on this topic
Alternatives Considered
Reduces database sprawl, ETL costs, infrastructure expenses, etc. Supports horizontal scaling, unlike PostgreSQL & Aurora, and real-time analytics and fast transactions (HTAP), unlike Snowflake & ClickHouse.Handles high-volume workloads with thousands of concurrent queries. No need for ETL processes, unlike BigQuery & Snowflake. Works with JSON, relational, and key-value data, unlike ClickHouse.
Read full review
Oracle Database is "the" serious database. There really is no competition in that field. SQL Database would be a serious competitor through the ease of implementation and the "no maintenance," but since it's too expensive for "normal" use (medium to small applications), it just priced itself out of the market, so to speak. Nevertheless, we do have 2 or 3 large applications that are highly integrated in azure, and for those it's just too easy to use SQL Database instead of the on premise Oracle Database with VPN gateways etcetera.
Read full review
Scalability
Very reliable. Coming from mariadb, singlestore has made our application more reliable and faster!
Read full review
No answers on this topic
Return on Investment
  • Lower operational complexity - Installation and maintenance is pretty easy
  • Object scale when used can compete with Traditional Warehouse Systems like Teradata, Netezza, Greenplum
  • Adds lot of value to the business like couple of operations which never worked in traditional DBMS including HANA, Oracle In Memory, SQL Server In Memory just flew in SingleStore
Read full review
  • We don't need a dedicated SQL dba because so many of the database maintenance operations are managed. A huge positive not only in budget but time constraints.
  • The ability to scale quickly is the biggest positive as our data needs change constantly.
  • Easy to migrate from legacy tools and systems, saving us on the need for redevelopment.
Read full review
ScreenShots