Oracle SQL Developer Reviews

It is the easiest and quickest way to see the data in the system.

It's quick and rapid.

You get to the point and you can choose what you want to do. It gives you a complete picture of the database.

It should be more Mac friendly.

It is simple.

It is scalable. Although, we don't use it to get large data, still it is scalable.

The technical support provided was always good.

Since it is a Java based, it is more compatible with Mac.

I think it was an easy process.

Cisco is an Oracle shop. So, we have more product support than anyone else, which gives a lot of comfort to move it over.

It's an independent platform. You can use it anywhere.

It's good, scalable and a lot of times, it works as-is. We have very few calls to support. It is Mac compatible team, and it is Java based.

In my work in BI development I find that Oracle SQL Developer is the main tool in my tool box. I can use it in so many ways: When I am designing a solution the ability to reverse engineer and diagram a database is an enormous boost to my ability to understand data relationships, in fact the latest versions allow me to see the physical model directly in the 'table viewer'. The way in which the product links into my version control system and helps me manage my database object source (DDL, PL/SQL etc) is a real plus. The way in which the 'cart' feature helps me create a simple way group objects to deploy and finally the way that I can use the tool to help me tune my code for optimal performance using the SQL monitoring and query plan features - the ability to compare plans and traces by a simple right-click is simply amazing.

And if that was not enough - true data-nerds can work with Oracle OLAP and Data Mining directly in the product

SQL Developer has allowed me to produce excellent system documentation, rapidly optimise query performance and allowed me to create top-quality source and object deployment methodologies.

The GUI ‘navigator’ screen uses different icons for partitioned, indexed organised tables. temporary and of course conventional tables. This allows users to see at a glance the type of table object in use. This is not the case with indexes in the viewer - they all look the same so can’t tell if it is a bitmap index, a unique index, a partitioned index or what. A minor irritation, not a big problem.

Since the first pre-released version (Raptor).

None - if you have the correct Java SDK on your system you are good to go after unpacking a single zip archive.

This is so simple to implement - almost anyone could do it.

The beauty of this product is that is free to those with an Oracle database.

The most valuable features are being able to see all of the database objects – every single one of them – within each schema; being able to edit them; and being able to create objects. My whole job is done in there.

The solution I've created is revenue forecasting and our organization goes to Wall Street with the earnings call, with the forecast. So it's very valuable to the finance department.

I would say the layout should be improved. I've also have used PL/SQL Developer, and I like the layout, the landscape, of that application better than SQL Dev. Even though, in SQL Dev, you can highlight every single view and save the DDL, where you can't do that in PL/SQL Developer, the layout is what I would suggest as far as an area with room for improvement.

SQL Developer is very stable; never had an issue.

I only work on a Lenovo Windows machine. I don't work on Apples. I don't know if it's scalable there or not.

I have used technical support for this solution and they get back within 24 hours with a user-friendly answer. It's very good.

The company actually was using Toad, by Quest, and it's very expensive. It's user friendly but a developer shouldn’t need a super user-friendly solution. Also, SQL Developer's free; it comes with the install, the Oracle client.

When I’m selecting a vendor such as Oracle, the most important criteria is look for is reliability.

I installed it: downloaded, installed, configured; very easy.

I chose this product because it has a solution for all our needs, such as reporting, the PI, the development, the jobs themselves run on/out of the Oracle database. It was the total solution.

Read as much as you can. Just use it. I've been doing this for 25 years, so it's very easy to me. The more you do it, the easier it is.

It's just the best out there.

They've done so many things that have made that product just so great. The most valuable features, what I tend to now use the most, outside of the change they've made in the IDE itself, are how it's become more flexible and the maturity in the IDE itself. It has the ability to manipulate code right there on the screen. The formatting and the UI's getting a whole lot better. That's part of it.

As far as a specific valuable feature, outside of just mentioning how it seemed the tool itself matured overall, is its modularity. I'm now able to split out windows that I couldn't do before. Basically, exploiting Windows features that are now available, it lets me kind of take advantage of having a really huge 30” screen. Now I can pull up and have multiple views of code running, and I'm able to lock that code, lock the results of queries in, so that I can see the differences between the things that I'm doing and if I wanted to change something, what the outputs will be. That's been a really good feature that I've appreciated in SQL Developer.

When I was reviewing some things in SQL Developer, one of the things that jumped out at me, especially in a former job a couple years ago, was the Cart feature. It allowed you to really streamline processes. Our process before was my developers would create some type of PL/SQL script, it could include DDL, a creating table, grants/permissions, obviously the scripting behind that, and we would take those series of files, we would put them on a shared drive on our network where our DBAs could then go get those files, and then promote them into our production environment.

The Cart feature, which came out I think around version 4 or so of SQL Developer, allowed you in the tool itself to select all of those components that developers had been working on, patch them up into a file that included everything our DBAs would need in order to roll that onto production. We can then just send them basically this shopping cart. They could take SQL Developer on the back end, open that cart up and basically deploy that through whatever environment.

That really allowed us to make sure that all the files and all of the components of any particular project we were working on were together, because we're not trying to copy this SQL file and put it over here, and this database definition, this table definition file in SQL over here, and grab a bunch of different things and stick them in a shared drive. We were able to use the tool itself, SQL Developer, to do that packaging for us and then with all the surrounding code needed to actually deploy that, and just pass that off to our DBAs who can then just execute that series of commands. They didn't have to come back and ask us anything. We eliminated kind of the question-answer piece between what the developer wanted and what the DBA was trying to do, because we were able now to encapsulate all of that into this Cart file. The Cart file included all of the coding that we needed our DBAs to execute on, to deploy into our development production environment space, to put our changes in. It really streamlined a process that we had integrated.

There are always areas of improvement as it relates to the tool's ability, the process that you need to go through in order to connect to some of the non-Oracle databases. You've got to go find the drivers for connecting to a DB2 database or connecting to even a MySQL database, which is now all by Oracle. Some of those components are just not included. Some of the tasks that the DBAs have to do could be worked out a little bit more.

They've done a great job with providing or producing a dashboard screen; very interesting metrics that you want to see as it relates to what's going on with the database. That's great, but - and this is just feedback that I get from DBAs - some of the features that it deals with, with their role in exploring what's happening in the database, are not there. That dashboard screen that you can now pull up has definitely moved in the direction that allows DBAs to go through there.

Growth in a monitoring perspective is something that I would like to see as it relates to the tool. It gives the developers the ability to say, "Oh, I ran the SQL and here it is outside of the normal suite of tools that Oracle has"; just something very simple to look at and go, okay, I can see how this is impacting the system.

Growth in those areas is where I would see the biggest benefit, but also a very big benefit in how I can connect and say, "Let me see what's going on," and I actually can get a snapshot of what's happening at that moment in time, what opportunity in the future could we push that, as it automatically refreshes that information.

I’ve probably been using SQL Developer as far back as 2008.

From a performance perspective, we tended to see Java version compatibility issues. If you had a 32-bit version of SQL Developer for whatever reason when we were running in a 32-bit environment, you had to go download the 32-bit version of Java. If Java at that point would release a new update and you didn't get it and you wouldn't download it, the new version of SQL might not work.

The 64-bit version comes prepackaged with the JDK, so if you download that, you get it all. There's no separate install; it's just included in the ZIP file. The ZIP file's a little bit larger, but you know that when you pull it down, you're going to have all the pieces that you need.

With some organizations, it might not be feasible to have a second JDK installed on the machine due to compatibility issues with other applications.

But I think this is kind of common on the Java platform across the board; maintaining those versions when you've got one application that needs version 1.6 and SQL Developer needs 1.8. You've got to juggle those two things around and do some internal system configurations to make sure it is looking at the right version.

From a scalability point of view, because it's just an install on each machine individually, scalability is not really an issue. Because we're in a network environment, we're able to actually have SQL Developer share file system space. We can point SQL Developer to the shared space. Those types of things weren't really an issue. It's not like we add people to using the one instance.

SQL Developer is able to handle hundreds of thousands of rows and columns. I haven't seen any instance where SQL Developer itself is the issue. Most times, what we've seen is that, either I've got a memory constraint issue on the machines, so I can only load in so much stuff, and SQL Developer has a configuration point that limits the amount of rows you get back from this database to 500, or whatever that is.

You can address system limitations. We've run into experiences where people say, "Oh, this is running slow." It tends to be slow because a bad query that has been written, and SQL Developer has tools to go in and look at the SQL and start doing troubleshooting. Or, you're trying to run something big in the middle of a financial close, and actually the resources you're trying to reach are being consumed by other things.

As far as running SQL Developer itself - outside of the Java compatibility issues where you might see SQL Dev not find Java or hang because it doesn't have the right version - the actual ability for the tool itself to grab the data, I have not run into a scenario where it's SQL Developer, so much as I have run into it's actually the machine that I'm using that may be limited in resources.

We use the community as opposed to opening a ticket with Oracle, for a couple of reasons. Part of it is there's a certain part of the community using SQL Developer that because it's free doesn't understand that you can go and submit an SR for a patch fix in SQL Developer. Some of that may be why you get certain comments like that.

However, and this is more of a Oracle user community plug, the people that are using these tools are very open with helping you solve problems. The solutions that you get back are typically a lot faster than going through the structured support process, where you submit a service request, somebody says, "Okay, send me this back," and then you send it back and a couple days later somebody... You've got people that are actively out on Twitter and in the communities on forums that are just doing this stuff because they love doing it, and responses you tend to get involve a variety of options, and you tend to get those options a lot faster than going through the SR process.

If there's a bug that you want to report on SQL Developer, the only way to go about doing it is to open an SR. But for, "Hey I tried to do this in SQL Dev, and I just can't get it to work," put that on Twitter, put that in the SQL Developer community, and you'll have a dozen answers almost instantaneously. This is not because I know Jeff Smith, but he's very active in those community spaces as well, and is very good at responding to issues that people have. It's actually really good to have the product managers and the product developers actively looking at the communities that people are using to get these questions answered.

Part of it is definitely driven by the folks behind the scenes that are pushing that particular department down.

When I started in this particular organization's IT department, a number of people were running SQL Developer and a number of people were running Toad. Outside of the fact that Toad costs money and SQL Developer is free, the great thing about SQL Developer at the time and even now is there wasn't really a need to deploy it out. You just go to Oracle's website, download SQL Developer, and unzip it. There wasn't really a need to have a rollout process of a network of applications. Because of the simplicity of it, and how you delivered really made that a non-issue.

While it might seem that Toad has stronger DBA options, I think that the real issue is that the DBA options are buried in SQL Developer as opposed to kind of front and center. The DBAs were the ones who used Toad and the developers were the ones that used SQL Developer.

When I started work on the development side, I thought, "Oh, okay, this is what we're using." When they issued you your computer, they’d say, "Go download SQL Developer and start using it." That was really how my introduction to SQL Developer really started.

I wasn't involved in the evaluations. I had a larger team; there were two DBAs and six or seven total developers all using SQL Developer. At least from the perspective of what our DBAs were using Toad for, we were able to demonstrate that SQL Developer had the same capabilities. It came down to, for those capabilities, you've got to go up and hit view and find the DBA tab, and you have to select the DBA tab and then you add the database to the DBA tab and then you get these features.

For somebody that's probably used to using the competing product, Toad, those links are on the main page, per se. One of the challenges was with the push back - "Oh, SQL Developer doesn't do that," - and we had to say, "You have to go here, here, do this, do that, and look, here's that same stuff right here."

We were able to win the battle between it costing a license fee to do this, or you can go configure SQL Developer, which is easy, to fit your needs and use it instead. That was the thing that allowed us to start using the Cart process, and a number of other things to streamline that whole migration of application and tools through our development cycle.

It has done everything that I needed it to do, and it doesn't cost you anything. That's the first pitch. Then, when you start saying, "Okay, well how do I get involved with SQL Developer, how do I take advantage of it?" One is, you can go to the OTN website or the downloads at the Oracle.com website, and you can download a copy. It's an install. Actually, it's not an install; it's an unzip. You don't have to worry about specific issues such as not being able to install software on your computer because of corporate policy; you just unzip the file you wanted.

Then I follow that with going back to this community perspective; there are tons of blog posts that I would say, “Do a search on Google for ‘How to do’ whatever it is you're doing in SQL Developer. You're going to get something back.”

The tool itself is very intuitive, and you can download documentation from Oracle's website. For, me the real documentation is what the people who are using it every day are pushing out; here's how I did or how you do these particular tasks. I've written several myself on how to connect to a database using SSH. There are a number of “How do I make this extension to run within SQL Developer”, which is a cool thing. I can write an extension and make it part of SQL Developer, if I wanted to use SQL Developer to monitor something. I have the ability to write code that I can then incorporate into SQL Developer, and have it do some additional task that it didn't come delivered with. Great tool, great feature. You might not see that in anything else.

Know what is unique to SQL, obviously, because it's a tool used to develop databases, develop applications within the database environment, and because you have to know how to configure SQL Developer to connect to databases, you might want to brush up on what that means as it relates to your database environment. A connection string in an Oracle database is going to be different than if you're trying to connect to a MySQL database, a TimesTen database, a DD2 database, or even MySQL Server. Being familiar with what you're going to connect SQL Developer to is very important, as it will save you a lot of the frustration of, “I don't see what's going on, I don't know how to do this.”

Get familiar with the PL/SQL debugging tool within SQL Developer. It allows you to skip through your code, so you can see what the output is going to be, or what these fine variables contain as you go through your codes. It obviously helps you with troubleshooting. It'll add optimization of your codes. Take advantage of the ability to, as I mentioned before, to separate out your codes so that you can see the before and what your changes are.

There are a lot of features. The editing, get familiar with editing within the IDE. It does block editing, all kinds of things that let you format your code for presentation purposes. Just kind of think about what your development environment would look like, and just download SQL Developer and just go through those things, and get familiar with them so when you're actually getting ready to say, "Hey, I'm trying to convince corporate that this is the route we need to take," you can then lay on top of what you're supposedly doing with how SQL Dev can actually help you achieve those goals.

I noticed that many of the small features are the biggest time-savers like:

• ‘Copy Selected Column Header(s)’ in the data grid
• Persistent highlighting of rows or cells in the data grid
• Search-and-replace with its smart options
• History (of statements and files)
• Splitting windows and document groups, pinning

Personally, being a nosey person, I love the Statements-Log Window, which shows every command SQL Developer sends to the database.

I have used it for three years.

Deployment was the easiest I ever encountered:

1. Unzip
2. Optional: find ide.conf, set the language to ‘en’
3. Optional: change NLS settings
4. Ready

Version 4.1.3 64-bit is very stable.

I had some problems with an older version freezing several times a week, but that was about two years ago and has hardly ever happened since.

Technical support is excellent. There’s the fast track via Twitter, but most of the time, I found the answer on Jeff Smith’s blog or Oracle Tech Net (OTN) before making a fool of myself by asking. Jeff has solved many of my problems “by unsent messages”. ;-)

You get very fast support on OTN or Twitter.

In different projects, I used to use TOAD and PL/SQL Developer.
One of my customers decided he didn’t want to spend any money on tools, so SQL Developer was my choice... I guess I have to be grateful :)

Initial setup was very easy, see above.

I tried Raptor ages ago (and didn’t like it at all), but now I am a converted SQL Developer enthusiast.

Read Jeff Smith’s blog. If you think a feature should be there, investigate. Quite likely, it’s already there; maybe you just overlooked it. If it’s not, open a feature request at sqldeveloper.oracle.com. Learn a handful of shortcuts (or two), it will improve your efficiency enormously.

The speed with which you can build SQL statements and PL/SQL code has been very valuable. In addition, it simplifies how we manage database objects and connections to different data sources.

It has reduced the time it takes to manage data. We use the product for data analysis, building SQL statements to construct reports, and analysis and optimization of SQL statements.

The interface could be friendlier for the DBA by having the dashboard show real-time statistics from the database engine. It could also give details from active sessions, details about PGA, information about background processes like DBWR, LGWR and RVWR, alerts when you pass thresholds, logical reads, physical reads, and direct physical leads.

We have used the product for about 2 years.

It has been stable.

There have been no issues with scalability.

Customer service is very good.

It has been excellent for us.

Initial setup is simple. Once you have a connection to the data source, you can begin working. We implemented in-house and there were no issues.

It is a very good investment for the benefits that it offers.

Download it, install it and never stop using it. I would give it a ten out of ten.

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.

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.

I have been using both SQL Developer and SQL Developer Data Modeler for six years.

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.

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.

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.

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.

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.

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.

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.

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.

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.

I've actually been using a similar tool for probably 17 years, but we switched over about four years ago to SQL Developer. A lot of these features I had used previously but there are advantages to SQL Developer. I guess just cleaning the database, looking at the information about your objects and the database, doing data manipulation. That's what I use it most for. DBAs would use it a little differently, maybe, but for me, as more of a developer or business analyst, it's pretty simple, just kind of your gateway to the database.

The biggest thing is really the cost savings as opposed to using a competitor project or competitor application to SQL Developer. The competitors cost significantly more.

Since Oracle SQL Developer is free, we no longer incurred the cost of the previous tool. There was also benefit to our organization in that the SQL Developer community is very active and growing, so there is a lot of resources available to us.

There are a lot of options and I think, as with any tool, making finding those options the easiest would be something that that this tool could work on. Sometimes it kind of takes a while to go through and remember where different options are. I've seen as we've gone through different versions of the tool, they're continuing to get better at that.

There's always going to be streamlining, and one thing they could improve is the installation. Even though it installs easy, there is a lot of Java behind the tool. It seems like some of the Java is more memory-intensive. Sometimes I feel like the Java side of the tool kind of gets in the way.

I think I’ve been using it since 2012.

A consultant that started working with us knew part of the product team personally. I first got introduced to Jeff Smith, Chris Rice and others on the product team via Twitter. If you follow them and interact with them on Twitter, there's a lot of resources. Jeff Smith has a blog, where he has a lot of SQL Developer tutorials. Sometimes, I ask questions on those channels, and there's a Facebook page. I've searched a lot on the forums and they also have something called SQL Developer Exchange for requesting enhancements.

There's a variety of ways that I've reached out. I feel like it's a very active community, so a lot of SQL Developer users are willing to help each other. A lot of times, I start with the social media side.

There's really nothing that I think is lacking. I've been very active and very vocal. That's probably one reason why they reached out to me to get a better view. Sometimes I have worked through, "Hey, why does it work like this? Can this be changed?" There have been things that the product team has changed because of some of the feedback that I or my team has given, so we've had a really good experience working with them.

The decision to switch to SQL Developer was basically about the cost. We were using Toad, those products. I had been using it for 13 years or something. I had gotten so used to it, pretty much everybody liked it and we were productive with that tool.

When we started investigating SQL Developer, it was given to us kind of as a challenge: Is there anything that Toad did that is imperative to your job that SQL Developer does not do? We couldn't find anything. There were some differences to get used to, different shortcut keys and so on. Just like switching from a PC to a Mac, you get used to it and there's really nothing that it can't do. It's a great way to save a lot of money.

I was involved in the deployment. The harder part for us has been putting these on a shared terminal server which is not always what Oracle recommends. Sometimes, when working on those shared servers, there are certain versions of the Oracle client that are needed for different versions of SQL Developer. Sometimes we've had to take that extra step to upgrade the Oracle client, but overall it's a simple install. Most of our problems have been from, again, a shared environment perspective.

We looked at a few other products and there have been different consultants that have come into the company that might use SQL Workbench or PL SQL Developer, but I think in general most of us are just sticking with SQL Developer. I haven't done a full analysis, because there just hasn't been a need. There's not really been anything that, to me, has felt lacking.