A Quick 4.1 Trick: SET SQLFORMAT

thatjeffsmith SQL Developer 52 Comments

One of your favorite SQL Developer ‘tricks’ is the ability to pre-format query output. So instead of getting standard output back, maybe you want query results to come back as CSV. But using that requires you to add code to your existing SQLs. Maybe instead it would be cool to set the overall script output format? Now that we have …

30 SQL Developer Tips in 30 Days, Day 20: See, Click, Goto Error Messages

thatjeffsmith SQL Developer 0 Comments

This question comes up very frequently: Why can’t I see my compilation errors when I’m working with PL/SQL? Because you are either: using the wrong editor, or not asking to see the errors SQL Developer is the PL/SQL IDE for the database. So we obviously need to have those ‘fancy’ IDE features like a debugger, compilation message support, profiling, bookmarks, …

30 SQL Developer Tips in 30 Days, Day 13: Executing Very Large Scripts

thatjeffsmith SQL Developer 2 Comments

What’s a very large script? That’s a subjective question, and the answer will depend somewhat on the hardware specs of your machine. I got this question yesterday: @thatjeffsmith is there a limit to the number of lines I can paste into the code editor in SQL developer? — louise mcscootash (@metalouise) September 12, 2014 I enjoy these questions. They’re 99% …

30 SQL Developer Tips in 30 Days, Day 8: Use the Cart to Build Deployment Scripts

thatjeffsmith SQL Developer 7 Comments

Let’s say you have some objects you need to quickly create somewhere else. And you want to it such that it can be scripted/scheduled. I am using the Cart right now to build out a demo environment for folks that want to show off some SQL Developer features. For instance, I’m building a ‘shopping list’ to cover things such as: …

30 SQL Developer Tips in 30 Days, Day 4: Statement Execution

thatjeffsmith SQL Developer 3 Comments

A few quick things to remember: Try to always use statement delimiters Even before I go to execute this ‘statement’, SQL Devleoper is telling me I have a problem. The grammar check is failing. Notice those red squiggle lines? They actually mean something. So, add a semi-colon, or do this: Know the difference between executing a statement and executing a …