I love how easy it is to test things there at any time, from any device. I still feel the need to go back to SQL*Plus from time to time, though.Īnd the third tool I’m really happy to have access to is Live SQL. It is just too feature-rich and easy to use, that it became my tool of choice in most situations. Twitter: days I mostly use SQL Developer.
I’m doing stuff with Python now but if I could only pick 3 those are the most important to my work today.Ĭarlos de Leon: SQL Developer, SQL*Plus, LiveSQL Website: Twitter: think mine are sqlplus, Textpad, Toad. The top three tools I use frequently areĢ. Twitter: focus now-a-days is troubleshooting performance problems and database advisory.
Well, I normally use SQL Developer, SQL*Plus, and PL/SQL Developer is also a very good tool.īiju Thomas: SQL Developer, Cloud Control, EDB360 My three tools are SQL*Plus for running scripts/traces/explains etc, Komodo Edit/Notepad++/vi for development (depends on what O/S I’m working with at the time) and SQL Developer (general querying/browsing, including some customised reports).Īlexander Anokhin: SQL Developer, SQL*Plus, PL/SQL Developer I’ve listed them all below, along with a summary of these tools at the end.Īdrian Billington: SQL*Plus, Komodo Edit/Notepad++/vi, SQL Developer Let me tell you, the insights I received from these 50 database experts were nothing short of amazing. If you could only use 3 tools as an SQL developer or DBA, what would they be? However, there are people who have a lot of experience working with SQL, and I’ve asked 50 of them to share their answers to this question: It’s hard to know which tools are useful, will help you get the job done, and are widely used so you can get support easily. This will become an important part of keeping the versions up-to-date in the organizations, now that you guys have increased the frequency of releases.There are a large number of tools available for Oracle SQL developers and DBAs to use.
It would be nice if Oracle SQL Developer team would provide us with an MSI such that it would take care of (1) detecting the presence of the appropriate JDK pre-req and if not found, it would install it quietly, (2) detecting the presence of older SQL Developer version and if found, it would un-install it quietly and seamlessly and install the newer version quietly and seamlessly. What if the user had manually installed the previous version of SQL Developer at C:\Downloads\sqldeveloper folder? How do we know where the user actually installed it previously, so that we can remove it and always stick with C:\sqldeveloper folder? What happens if there's already a folder like that existing. Suppose the package is developed such that it would always extract the contents of a given new version to folder C:\sqldeveloper folder. Plus, after we find a way to auto-detect the installation folder, we need to do more steps to ensure the pre-reqs like JDK is installed or not disable the older version of SQL Developer by renaming the folder perhaps, before deploying the newer version of SQL Developer.Īny guidance to automate all this would be what we're trying to do Jeff, however, pushing the package and automating it with all the "smarts" of (1) detecting where the previous version is installed, (2) remove the older version, (3) push the newer version along with its pre-reqs (JDK) is not that obvious.
If a user already installed an older version of Oracle SQL Developer by manually downloading the ZIP file and then extracting its contents to some folder path, how can we read the path to this active folder? Because it is not anywhere in Windows Registry, so we're having an issue with automating a package for quick deployment. Having to manually perform this task for 100 PCs is taking a lot from our resources.
I wish there was an easy way to deploy such that it would take care of detecting where SQL Developer zip contents were extracted to which folder and where is it actively running from and infact, be able to seamlessly upgrade it in silent/quiet mode on Windows. Now that Oracle SQL Developer is being released frequently every 3 months, we're trying to see if we can package and automate the deployment of this tool through to several Windows workstations (~ 100) in our organization.