Oracle SQL Developer is an integrated development environment (IDE) which provides editors for working with SQL, PL/SQL, Stored Java Procedures, and XML in Oracle databases.
N/A
SingleStore
Score 8.3 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.
Almost all development activities (the tool is called "SQL Developer", not "DBA Toolset") can be done easily and quick with [Oracle] SQL Developer. From data model creation (tables, views) to development (creation of procedures, functions, packages) and then testing (SQL Developer includes an easy to use debugger), all tasks can be performed in a single tool.
It may not be as complete as other solutions for DBA tasks like instance monitoring, but it is usually OK for development and testing environments if you want to do some basic troubleshooting.
Good for Applications needing instant insights on large, streaming datasets. Applications processing continuous data streams with low latency. When a multi-cloud, high-availability database is required When NOT to Use Small-scale applications with limited budgets Projects that do not require real-time analytics or distributed scaling Teams without experience in distributed databases and HTAP architectures.
Object Browser in SQL Developer allows you to explore the contents of your database using the connection tree.
The SQL Worksheet is an editor that allows for execution of SQL statements, scripts, and PL/SQL anonymous blocks. SELECT statements can be executed to return results in a spreadsheet-like 'grid' or can be executed as a script such to emulate SQL*Plus behavior and output
DBA Console allows users with administrative privileges to access DBA features such as database init file configuration, RMAN backup, storage, etc.
Inability to run multiple queries on the same database. You can only run one query on a given database.
Analytical models created from complex tables isn't accurate, and needs work.
Inability to view multiple tables of a database side-by-side. When trying to find correlations between tables, it would help to be able to see them at once on the same page.
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.
Oracle SQL Developer is very easy to use and there are a wide range of courses available which can help you get started just within a day. Data can be exported in multiple formats based on user requirements. Organizational data can be stored and management effectively using Oracle SQL Developer. All the data, tables, sequences, indexes can be easily created and updated in Oracle SQL Developer.
[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.
SingleStore excels in real-time analytics and low-latency transactions, making it ideal for operational analytics and mixed workloads. Snowflake shines in batch analytics and data warehousing with strong scalability for large datasets. SingleStore offers faster data ingestion and query execution for real-time use cases, while Snowflake is better for complex analytical queries on historical data.
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
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.
I have started to use Toad for Oracle recently because it is easier to sort and filter results, due to their memory sort feature that puts the results from your query in memory so that you don't have to rerun your query. I have used SQL Developer to easily update records in tables that I need to fix. I haven't found an easy way to do this in Toad other than writing SQL insert statements.
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 Greenplum and Gemfire was not good. Product team did not help us much like the ones in SingleStore who helped us getting started on our first cluster very fast.
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.
