Educating developers on what Oracle tools and products our team makes, hopefully.
Updated: 47 min 53 sec ago
New Name ! The first is a new name this EA it's named sqlcl for sql command line. However, the binary to start it up is simply sql. Nothing is easier when you need to run some sql than typing 'sql' and hitting enter. #./sql klrice/klrice@//localhost/orcl SQLcl: Release 4.1.0 Beta on Fri Jan 30 12:53:05 2015 Copyright (c) 1982, 2015, Oracle. All rights reserved. Connected to: Oracle
In SQL Developer, Jeff has shown in many tips & tricks talks and here on his blog how to get data from any select into a few formats. The most common I would say is csv. Nothing here has changed. Well, almost. What will be new is the html format is getting a facelift and a json format is being added neither are in the version of sdsql or sql developer that are on otn yet As expected
This is in the process of evolving but should be enough for anyone to give it a whirl. The idea is that for any given statement you may want to run something before and possible after. Here's a trivial example. I'm issuing 2 statements 1) a drop table and 2) creating a table of select * from v$mystat before each command. Then after I'm doing sql that shows me the changes from that point
First, we just put up a new build of sdsql. Go get it or the last thing here will not work. SQL is a great and verbose language so there's many ways to shorten what we have to type. As simple as a view or saving a script to call later with @/path/to/sessions.sql SDSQL is taking it a step further and we added aliases to the tool. Almost as if right on queue, John asked if we could add them.
SQL Developer is now up to version 4.1 and has had many additions over the years to beef up the sqlplus compatibility. This is used today by millions of users adding up to millions if not billions of hours in the tool doing their work. That means our support of core sqlplus has to be very full featured. One idea we kicked around for a while but never had the time to do was to make our
Writing sql or any code is an iterative process. Most of the time that means to see what you have done say 5 minutes ago means how big is your undo buffer or better is if you are in SQL Developer there's a full blown history. If you are in sqlplus, you are basically out of luck. History SDSQL has built in history and between sessions. We are still jiggling where it stores the history so
Getting ddl out for any object is quite simple. You can just call dbms_metadata with something nice and easy like select dbms_metata.get_ddl('TABLE','EMP') from dual; SQL> select dbms_metadata.get_ddl('TABLE','EMP') from dual; DBMS_METADATA.GET_DDL('TABLE','EMP') -------------------------------------------------------------------------------- CREATE TABLE "KLRICE"."EMP" ( "EMPNO" NUMBER
SQL Developer 4.1 is out for tire kicking. There's a lot of new things in there as well as some great enhancements. There's a nice shiny new Instance Monitor to get an overview of what's going on. Keep in mind this is in flux from a UI stance and the final may be quite different that what you see today. There's tons of data here and mostly all things have drill downs. Also, we took the