What is most valuable?
To me, the most valuable feature is the ability to quickly reverse engineer a database structure into a data model.
There's also a drag-and-drop feature that helps you build queries in SQL Developer, which has a visual query builder with it. I like that feature a lot as it has a number of options in the wizard to pick what type of query you're trying to build. It can build inserts and updates as well. I've used that quite a bit as well. That was very helpful for, I'll say, short-cutting the process of building queries. It helps me be agile.
How has it helped my organization?
Where clients of mine have adopted using the data modeler in particular, the teams are able to become more efficient because they have the data model to use as a reference diagram and documentation to the structure of the database. That made planning changes to the database, reports and things like that much easier to do, and less error prone. Whereas before, when they didn't have a model and they were having to guess at what the data structures were and do a lot of individual investigations. It took a lot longer to get things done.
It also allowed us to produce a data dictionary for the organization, which helped business users. I deal primarily in data warehousing and so from a business intelligence perspective, being able to publish a data dictionary to the business users was very helpful because it helped them understand the database that they're trying to pull the data from.
For how long have I used the solution?
I have been using both SQL Developer and SQL Developer Data Modeler for six years.
What do I think about the stability of the solution?
Especially in the more recent versions, I've not had any stability issues at all.
I don't have it randomly crashing on me, so that is good. Seems to work equally well on Windows and Mac OS.
Buyer's Guide
Oracle SQL Developer
January 2025
Learn what your peers think about Oracle SQL Developer. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,265 professionals have used our research since 2012.
What do I think about the scalability of the solution?
It seems to scale fine. If you're trying to return exceedingly large data sets into the tool for some reason to download, that could be a challenge, depending on the memory on your machine and the disk space you have to output it to. Oracle will perform the query just, depending on how well your database is tuned, but oyu do need space for the output.
On the Data Modeler side, people do run into issues with very large models with hundreds and thousands of objects, but there is actually a memory parameter and a config file which you can tweak to increase the amount of memory that the tool uses. That, of course, is then limited only by how much memory you have on the workstation you're using.
How are customer service and support?
Customer Service:
I've been quite happy with both SQL Developer and SQL Developer Data Modeler. They have incrementally added features over time. A number of things it was lacking in earlier versions they have added as a result of feedback from myself and other folks in the community. They're adding features all the time.
That's one of the things that I think is most impressive about it: the team that supports this tool. Product management and development are very responsive - via not only formal channels, but informal social media channels - at providing information on best practices and even taking input on changes where someone does find something that they think they would like to see changed. They take input in many ways.
On the OTN Data Modeler Forum, the lead architect and developers are incredibly responsive. In all honesty, they are more responsive than what I had seen in the past when I was working with customers that had big Oracle support contracts where you had to call Oracle support. The development team monitors the questions on the OTN forum and replies usually within 24 hours at the latest to questions people have the about the tool. I've used that forum for that entire time. Often asking how to do something and getting a very quick response on how to do it and in some cases it was, "Well, the tool doesn't do that, but here's a way you could do it instead," and actually getting workarounds.
There have been a number of cases where I've said, "Hey, it would be nice to see this kind of feature or that kind of feature." They actually came out in the next release. Very, very impressed with the development and product management team for this particular tool.
One of the product managers blogs multiple times a week on SQL Developer and SQL Developer Data Modeler, and he is on social media, on Twitter in particular, all the time and is very responsive to comments and requests and questions from customers.
Technical Support:
I've only gone to the OTN discussion forum, and gotten all the support I needed there. I've never opened a ticket of any kind formally through support.
Which solution did I use previously and why did I switch?
I had originally been an Oracle Designer user, which was the predecessor to Data Modeler and in the interim had used ERwin at one point as well and looked at Embarcadero. While all those tools were, I'll say, very functional, full featured, they were very expensive.
The bottom line is, when I first started using these tools, it was because I was in an organization that basically had no budget for doing this type of work, data modeling, so, they weren't doing it. Data Modeler is, for no other reason, the only choice because it was a no-cost add-on. It didn't cost you anything to use Data Modeler if you have an Oracle license so I began using it.
I actually used it against not only Oracle, but against SQL Server databases as well and found I was able to, in particular, do data warehousing. I needed to reverse engineer source systems that weren't in Oracle and often were in SQL Server, and then go forward designing a new data warehouse from there. I was able to pretty easily, again with some help with the development team, figure out how to connect both SQL Developer and SQL Developer Data Modeler to Microsoft SQL Server databases. They did, indeed, design it to do that, so it was not completely database agnostic, but it did allow you to look at some of the other major databases like SQL Server and DB2. I found that very useful to be able to conect with both of those tools, especially helpful in doing data warehousing.
How was the initial setup?
It is by the far the easiest tool from Oracle to install that I've ever seen. When it first came out, I did a presentation six weeks after getting my hands on it and the presentation started off with, "Well, let's first install it," and it was one slide. Download the ZIP file. Unzip it. You're done.
On SQL Developer, the only additional thing you have to do is set up the connection to the database. Assuming you already have a database in place, it's a wizard. You go and put in your credentials and it connects and you're off to the races, able to query data in the database and make changes to the database.
With the Data Modeler, it doesn't require a database connection. If you were going to design something from the ground up, you literally unzip it, start it, and create a new model. The longest part of that is downloading the ZIP file, so depending on your connection, that's how long it takes to install it. 30 seconds to unzip it and open.
What about the implementation team?
It's easy enough to install and try, that you ought to just do it. Then the next thing would just be look at a couple of books available on the product, on the Data Modeler product in particular, if you decide to go down that route. Otherwise, there are several people like myself and the product manager who blog about the products. Follow the experts on social media to get your answers, but the first thing is to just download it and try it and start asking questions.
Which other solutions did I evaluate?
I have not considered switching to anything else. I see no reason. I'm an Oracle ACE Director, and using Data Modeler is the thing that I am known for.
What other advice do I have?
I am a blogger, The Data Warrior, and I have multiple blog posts on it about these tools. My most popular blog post was when I wrote, probably almost three years ago now, about how to connect Data Modeler to SQL Server. The second most popular blog post is the very first one I wrote about the Data Modeler. Every so often, I go back and have to update it because there's new releases.
Every client I have had and every organization I have worked for since Data Modeler came out and SQL Developer came out, I get them using it. I have had several organizations that were using Toad and when time came for the support renewal on those, I usually got them to convert over to SQL Developer.
Disclosure: I am a real user, and this review is based on my own experience and opinions.