September 30, 2019
Senior Systems Analyst
Duquesne Light CompanyUtilities, 1001-5000 employees
Score 8 out of 10
Overall Satisfaction with Oracle SQL Developer
SQL Developer is used at Duquesne Light Company to query our Oracle Utility Suite databases (CCB, MDM, MWM). We use it for standard selects, DDL and DML. It is being used across multiple departments in both IT and non-IT disciplines. It is also used to build reports. It addresses the need for a simple user-friendly database connection and querying tool for those who know how to write SQL and need information from the OUS databases.
- Easy to install.
- Allows users to write PL/SQL.
- You can't run more than one query against the same database at one time. This is a capability for TOAD.
- Sometimes it doesn't allow you to use parallel threads in query execution and the error message isn't very descriptive or explain why.
- Editing your display preferences could be a little easier. I had to watch several YouTube videos before I was able to figure out where those settings are kept.
- All systems analysts have an easy way to interact with the OUS databases.
- More tech-savvy business end-users have a user-friendly way to pull information from the databases.
- DBAs have to support both SQL Developer and TOAD since not all users exclusively work in SQL Developer.
We use both tools. It's partially a user preference-based decision but TOAD's ability to allow more than 1 query to be run at a time gives it an edge over SQL Developer in some users' opinions. I think if that capability were added to the product, most if not all of our users would exclusively use SQL Developer.
SQL Developer is well-suited for low to medium volume select, update, insert, and delete queries where the number of records touched is <1,000,000 records. SQL Developer is less suited for real PL/SQL development. Our software engineers use other tools to write and compile larger PL/SQL packages. It isn't a bad thing but it's something that could be looked into.