30EA1: Closing Query Result & Script Output Windows

It would be nice if you could close these output windows by middle mouse button clicking. You can close object viewing windows (tables, procedures) & SQL worksheet windows this way.
Thanks,
Justin

Yes, please, for consistency. I bump into this limitation also now and then.
Thanks,
K.

Similar Messages

  • Create SP that returns value and at the same time displays query result in output window

    I would like create an SP which will return the records from the table and also return value to my c# client application.
    For Example:
    Select * from employee returns all the query results in output window.
    Now I want to create an SP
    Create procedure Test
    As
    Declare @ret int,
    Select * from employee
    set @ret = Select count(*) from employee
    if @ret > 0
    return 1
    else
    return 0
    The above algo should return 1 0r 0 to c# client application and at the same time display all employees in sql query output window.
    Can u pls help in this regard.

    The above algo should return 1 0r 0 to c# client application and at the same time display all employees in sql query output window.
    Why?  and No!
    Why?  Your procedure generates a resultset of some number of rows.  You check the resultset for the presence of rows to determine if "anything is there".  You don't need a separate value to tell you this.  Note that it helps
    to post tsql that is syntactically correct.   While we're at it, if you just need to know that rows exist there is no need to count them since that does more work than required.  Simply test for existence using the appropriately-named function
    "exists".  E.g., if exists (select * from dbo.employee). 
    No!  A stored procedure does not display anything anywhere.  The application which executes the procedures is responsible for the consumption of the resultset; it chooses what to do and what to display. 
    Lastly, do not get into the lazy habit of using the asterisk in your tsql code.  That is not best practice.  Along with that, you should also get into the following best practice habits:
    schema-qualify your objects (i.e., dbo.employee)
    terminate every statement - it will eventually be required.

  • Close script output window

    So after YEARS of working with MS SQL, I'm now working with Oracle. One of the biggest problems I'm having is that in Microsoft SSMS, you can hit Ctrl+R to minimize the query results window.
    1) Is there a shortcut key to minimize the script output window in SQL developer?
    2) I would like to change the shortcut to ctrl+r as it's such habit by this point, but not sure what the name of the proper shortcut would be either.
    Thanks in advance for any help with this!

    Check this thread where it was described how it works, however i don't think you can change the shortcut.
    Re: Request "Hot key to show/hide result grid" = how was implemented 2.1.1 ?
    Hope it helps,
    Dani

  • 4.0EA1 - Copy/Paste in Script Output window on Mac is not working

    I'm running 4.0.0.12 on MacOS X 10.8.4, and I can't Copy from the "Script Output" window.  What I regularly do is generate some SQL using an SQL query, so I want to copy the output and paste it back into the Worksheet so I can run it.  For example:
    select 'alter tablespace ' || TABLESPACE_NAME || ' begin backup;' from DBA_TABLESPACES;

    This is a known issue and will be addressed for the next EA release.

  • Bug? 4.0 EA1 Can't select all in Script Output window

    This seems to be a small bug. Open a worksheet and enter any query. Run as a script (F5) and the output appears in the Script Output window. Click in the Script Output window to give it focus and type Ctrl-A to select all the output. The text selected is actually the contents of the worksheet, not the output. Right-clicking in the Script Output window also has no effect. It looks like the Script Output window can't actually gain focus?
    This is a bit trivial, but was annoying when I was trying to move some data over to Excel using a /*csv*/ type query.

    for tracking this is logged as bug 17164225
    B

  • EA1 - DBMS_OUTPUT prints to Script Output window

    All,
    I saw another post about the window switching from the DBMS Output window to the script window after a script is executed (I don't like that either), but this is different.
    My DBMS Output is being output to the Script Output window.
    Example:
    begin
       dbms_output.put_line('Hello World');
    end;Yields (in Script Output):
    anonymous block completed
    Hello WorldDan
    Modified Subject
    Message was edited by:
    dmcghan

    This is definitely a change from 1.2.1.31.12, where even running as a script the DBMS Output was displayed on the DBMS Output tab.
    However, while this makes DBMS Output inconsistent (where it appears depends on how you run it) it does make scripts that produce DBMS Output and other output consistent (all output goes to script output).
    For example, if you were writing scripts like the following (assuming the PL/SQL generates DBMS Output), the output will now be consistent:
    select count('x') records from my_interface;
    begin
    process_my_interface;
    end;
    select count('x') records from my_interface;
    With the way the DBMS Output and Script Output tabs are set up now, either DBMS Output or Script Output has to be inconsistent when in comes to displaying DBMS Output. I think that the way 1.5 EA1 works is inconsistent in a more manageable way (largely because reconstructing a single stream of output from more complex cases of the example above would be difficult).

  • Japanese charactor does not display in Script Output window

    I usging SQL Developper EA 4.1 on japanese Windows XP.
    SQL Developper EA 4.1 can not display Japanese charactor in Script Output window.
    How can I change font for Script Output window?

    If you change your prefered encoding in raptor to be utf8, this will work. There was an issue with MB chars in the feedback from statements like "create table XX processed" where XX was the japanese chars that would not show, but this has been rectified

  • Tabs (Results, Script Output, etc...) disappeared, how can I call back?

    Cannot get the result after executed stored functions now, how can I get them back? Or reset the layout?
    thanks~

    Deleting the [Windows user profile]\Application Data\SQL Developer\systemXXX\o.ide.XXX\windowinglayout.xml file should restore default settings.
    Hope that helps,
    K.

  • Query results window limited to 100 rows then 150 then 200

    Great product - I love this tool and don't mind helping to find the bugs in the prereleases like this.
    When I
    SELECT * FROM MY_TABLE
    in a sql worksheet, the results window initially only displays the first 100 rows.
    I can try to scroll down, but it stops at 100 rows.
    If click on Script Output window, the fetch count goes up to 150 and if I click back into
    Results window, I can then scroll to row 150. Click back over to Script Output and come back, now I'm up to 200. As long I scroll to the bottom of the Results window and click back and forth, I can increase the size of the results window by 50 rows each time. If I want the result window to show 2000 rows this will get real tedious real quick...
    Maybe a bug in dynamically resizing the result set?

    Hi gary,
    You may have already seen one or more threads like the following on the issue of increased memory overhead for the Excel formats:
    Re: Sql Developer 3.1 - Exporting a result set in xls generates and empty file
    Basically SQL Developer uses a third-party API to read and write these Excel formats. There are distinct readers and formatters for each of the xls and xlsx forms.
    There is a newer version of the API that supports streaming of xlsx Workbooks. Basically it achieves a much lower footprint by keeping in memory only rows that are within a sliding window, while the older, non-streaming version gives access to all rows in the document. The programmer may define the size of this window. I believe the newer API version was either not available or not stable during our 3.1 development cycle. Possibly a future SQL Developer version might use it.
    Regards,
    Gary
    SQL Developer Team

  • Script output headers

    Is it possible to remove the header from query results in the the script output window?
    select 1 AS dont, 2 AS need, 3 AS a, 4 AS header, 5 AS thanks from dual;
    DONT NEED A HEADER THANKS
    1 2 3 4 5
    I only want the row of "1 2 3 4 5".
    In SQL Plus, I arrange like so:
    SQL> select 1 AS dont, 2 AS need, 3 AS a, 4 AS header, 5 AS thanks from dual;
    DONT NEED A HEADER THANKS
    1 2 3 4 5
    SQL> set heading off;
    SQL> select 1 AS dont, 2 AS need, 3 AS a, 4 AS header, 5 AS thanks from dual;
    1 2 3 4 5
    SQL>
    However, 'set heading off' in SQL Developer gives "line 1: SQLPLUS Command Skipped: set heading off;"
    Is this possible? If not, can it be put in the request pile for a future release?

    Can't be done currently...
    Requests should go to the announced SQL Developer Exchange, so others can vote on them.
    Regards,
    K.

  • No Script Output

    Does SQL Developer have a query timeout? We often run queries as scripts and never receive the results in the script output window. We typically see the number of seconds a query takes (ie. 15.2343 seconds) to execute but no data. Any suggestions would be helpful.

    When using Execute Statement, the current query is executed (unless you have a selection) and the time is displayed on the toolbar, record count is displayed on the status bar and the query results appear in the Results tab. When using Run Script, the entire worksheet contents are executed (unless you have a selection) and the time is displayed on the toolbar, "Script Finished" is displayed on the status bar and the query results appear in the Script Output tab (which should be switched to by default).
    Scott - if you clear the Script Output before running as a script and then run your statement as a script, do you get anything at all on the Script Output? Also, you didn't say what your version details are (ie SQL Developer, JDK, DB, etc).
    theFurryOne

  • Script output font

    hello
    is there any way how to set non-proportional font in Script output window? It should improve result reading...
    p.

    I am not sure if this is configurable. I just wanted to explain why we did it this way. You can use 'SELECT' and this is the tab that displays 'DESC' so the proportional font ensures your columns are aligned.
    -- Sharon

  • Script Output cuts my querry

    Hello SQL Developers,
    I have a script that has some bigger output per querry (exactly it generates an XML)
    When I run this script (F5) it only outputs the first about 200 chars per querry, then it cuts and starts with the next querry
    For example:
    Xml Output
    <?xml version="1.0" standalone="yes"?>
    <Customers>
    <Customer>
    <CustId>100<
    Xml Output
    <?xml version="1.0" standalone="yes"?>
    <Customers01234567890123456789>
    <Custom
    Starting every querry for its own (Ctrl+F5) shows in the result window the correct result of this single querry without cuting somethink of.
    I've tested it with the computer of a classmate. There it works fine without any cut in the Script Output window. Maybe that's because he didn't update
    SQL Developer for more then a year. Maybe it is a setting I didn't found yet. Please can somebody help me?
    Edited by: WillardBL on 10.10.2012 13:48

    Hi WillardBL,
    Quite a few years ago there was a bug involving slow performance and/or Java OutOfMemoryException when displaying MySQL BLOBs, probably due to some issue with the MySQL JDBC driver. The bug was addressed back in SQL Developer 1.2.26.09 and is...
    Bug 5904607 - MYSQL RUN SCRIPT PERFORMANCE FROM WORKSHEET NOT SATISFACTORY
    At that time, a 4000 character display column size limit was added to circumvent the problem. It still remains and has not received much attention -- perhaps since VARCHAR2 is also limited to 4000, at least through the Oracle 11g releases.
    In your specific case, you are not reaching the 4000 character limit. You can try the following in the worksheet:
    show longwhich should show a default value of 80 if you never overrode it in your connection login script (Tools | Preferences | Database). So just
    set long 4000and try running the script that outputs the XML again. Keep in mind that set long
    Sets maximum width (in bytes) for displaying LONG, CLOB, NCLOB and XMLType values; and for copying LONG values.
    Possibly Bug 5904607 needs revisiting, but I hope the approach described will be sufficient to get you past the current problem.
    Regards,
    Gary
    SQL Developer Team

  • Formatting Script Output

    Why does SQL Developer ignore
    col name format a15 ?
    col name format a15
    col value format a15
    select name,value from v$parameter
    where name ='statistics_level'Each column length seems to default to 80 charaters.
    I end up needing to use the hortizontal scroll bar to see the results in the Script Output window.

    "col" is a SQL*Plus command. SQL Developer does understand a few SQL*Plus commands, but most of the formatting commands like "column" are not supported.

  • 2 Dumb Questions: Toggle Script Output tab / Set Serverouput Toggle

    I use SQL Developer quite a lot, but I need some basic help
    I'm using SQL Develeoper 3.0.04
    Question 1.
    If I ever close [X] the Script Output tab/window, I have a huge headache trying to open/unhide it again. I can't do it!
    I've looked in the menus,
    Preferences / Keyboard shortcuts etc but I just can't see it.
    So how to a make the Script Output tab re-appear? THere must be a toggle somewhere.
    Question 2.
    In a previous version of SQL developer, I used SET SERVEROUTPUT ON.
    The output from all my dbms_output.print_line statements would appear in the script output window FOR THE ENTIRE SESSION.
    In this version that I'm using, everytime I run an anon block I have to preceed the block with SET SERVEROUTPUT ON.
    It doesn't remain ON for the entire session. It only affects the next block of code that I try to execute.
    An I doing something wrong?
    Thanks for any help.
    Stu

    Welcome to the forum!
    Thanks for providing the sql developer version. Functionality can, and does, change between versions.
    >
    Question 2.
    In a previous version of SQL developer, I used SET SERVEROUTPUT ON.
    The output from all my dbms_output.print_line statements would appear in the script output window FOR THE ENTIRE SESSION.
    In this version that I'm using, everytime I run an anon block I have to preceed the block with SET SERVEROUTPUT ON.
    It doesn't remain ON for the entire session. It only affects the next block of code that I try to execute.
    >
    Have you tried using the DBMS_OUTPUT window?
    Select 'view -> DBMS Output
    Then if you roll-over the '+' sign on the DBMS Output Window toolbar you will see that it says 'ENABLE DBMS_OUTPUT FOR CONNECTION'.
    Click it and all output should display in the window.

Maybe you are looking for