This post was inspired by two simple events –
- watching a co-worker use SQL Developer over Zoom
- an innocent enough tweet from Franck
I’m a horrible ‘back seat driver’
It bothers me to watch people do stuff less efficiently than they could be. This feeling, or reaction was the driving force behind my “SQL Developer, You’re Doing it Wrong” video. You can watch it now of course, but it’s about 17 minutes long. This post will be over in just 2 more minutes 🙂
I ALSO wanted to get down to the lowest possible level of this concept. What are the very, very basics of the UI/UX in SQL Developer? End of day, Franck just pushed me to ‘get busy blogging, or get busy dying.’
1. To run a statement, just hit Ctrl+Enter
I was watching my co-worker, write her statement, then circle back, select the text, then use the ‘Execute’ button on the toolbar.
Absolutely NOTHING wrong with this.
And if you’re using statement delimiters, or if you only have a single statement in your worksheet, it’s completely unecessary.
2. Avoid the ‘Clear’ button, just use Clear Screen
I use this all the time, and so does Franck!
As you’re testing a snippet of code, you’re going to be making changes and running it, over and over again. Now, sometimes you’ll want that running log. But most times, not so much.
3. Organize your connections
There’s really 2 tips here. The first is, give your connections GOOD names. The second is, organize them.
The easiest way to do is this is to add them to a folder, or even subfolder.
4. Quickly Clone a Connection
I’ve seen people do this so many times…you have a connection to one database. You want to add a second connection to the same database. They start from scratch!
No, it’s easier than that. Just edit an existing connection, give it a new name. We don’t ‘nuke’ the existing connection, we’l instead create a new one with the new name, and the original one remains.
5. Avoid the connection tree if you can
There’s nothing wrong with the Connection Tree. Tons of features are available there. It’s also the easiest way to explore the contents of your database.
But what if you don’t need to explore? What if you simply want the DDL for an object, or maybe a list of indexes or foreign keys?
I have two ways to get this information, faster than you can get it by clicking around in the tree.
Use the DDL command, and use the INFO command. We built them for SQLcl, but they’re also available in SQL Developer and SQL Developer Web!
Maybe I should start a Twitch channel?
Instead of killing the bad guys on my PS4, you could watch me kill bad SQL or create REST Services.
Yes, I’m joking. But watching people build a website or write a program or navigate the BASH always captivates me. What are they doing, and how are they doing it so quickly???
If you have suggestions or have a tip you’d like to share – leave a comment!