Scroll to bottom of query results

SQL Developer 1.2
DB 9.2.0.7
Is there any way to quickly get to the bottom of the query results? I'm transitioning off from SQL Navigator and use this feature all the time. Most query results are many many screens long so this is a very useful feature.

Although encouraged to filter and/or order your result set to conserve I/O and memory, you can always scroll to bottom with ctrl-end or ctrl-pgdown.
Regards,
K.

Similar Messages

Bug: the query results dialog extends outside the screen boundaries

Hi, I observed this bug on MacOS 10.5.5 running Eclipse 3.4.1 with FlexBuilder 3.0.2 installed. Steps to repro:
1. make FlexBuilder full screen
2. open an MXML document
3. make the editor full screen (double-click the editor's tab)
4. select in the text editor the name of a Flex SDK class (e.g. Window, Button, ...)
5. scroll the editor window so that the selected text is near the bottom of the screen
5. click the Blueprint button, or type ctrl-B
Result: the Blueprint query results window is only partly visible, most of it is below the bottom of the screen
Expected: the query results window auto-positions itself to be fully visible

Thanks for trying out Blueprint and giving us feedback!
We have filed a ticket for this bug and will do our best to address it in the next release!
Mira Dontcheva
Research Scientist
Adobe Systems

SSMS Addin - How To Access Query Results Grid

Hi,
I want to access Query Result Grid(Results) in SSMS addin but I did'nt found anything.
How can I access Query Result Grid, Rows, Columns and Cells when I executed a script?
Thanks.

SQL Server Management Studio currently supports query execution results to be displayed in three different ways: Results to Grid,
Results to Text and Results to File.
By default SQL Server Management Studio is configured to display query results in
Grid format. If you want to change the default to some other option follow these steps.
1. In SQL Server Management Studio, under Tools menu, click
Options as shown in the snippet below.
2. In the Options dialog box, expand Query Results, expand
SQL Server and then select General as shown in the snippet below. In the right side panel choose one of the three options shown below in the
Default Destination for results drop down list and click
OK to save the changes as shown in the snippet below. The changes will go into effect once you open a New Query window.
Query Result Options for Results to Text
In this format you have the option to display the results in a different tab as well as setting different output options.
In the Options dialog box, expand Query Results, expand
SQL Server and then select Results to Text tab as shown in the snippet below. In the right side panel first select the checkbox for
Display results in a separate tab and then select the checkbox for
Switch to results tab after the query executes and then click
OK. If you would like to also display the column name in the result set then choose the option Include column headers in the result set
as shown in the snippet below.
The options you can use in the Text format are:
Output format: - In the above snippet you could see that by default the output is displayed as columns aligned. Some of the other options that are available are Comma Delimited,
Tab Delimited, Space Delimited and Custom Delimited. If you choose the Custom Delimited option in the Output format drop down list then you need to specify a character of your choice for the delimiter in the
Custom delimiter text box.
Include column headers when copying or saving the results: - If this option is selected, then whenever the results are copied to clipboard or it is saved to a file the column headers are also copied along with the results.
Include the query in the result set: - The text of the query is displayed as part of query output under the messages tab.
Scroll as results are received: - If this option is selected, then the display focuses on the most recently returned records at the end of the results set.
Right align numeric values: - If this option is selected, then numeric values will be aligned to the right of the column.
Discard results after query executes: - If this option is selected, then the query results are not displayed in the reviewing pane.
Display results in a separate tab: - If this option is selected, then the result set after query execution will be displayed in a new tab instead of at the bottom of the query window.
Switch to results tab after the query executes: - If this option is selected, then after the query execution the screen focus will be set to the results tab.
Maximum number of characters displayed in each column: - This sets the maximum characters to display for any one column. So if you have a column that is 500 characters this will only show the first 256 if you keep the default setting.
Ref link :http://www.mssqltips.com/sqlservertip/2346/different-options-for-query-results-in-sql-server-management-studio/
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

Options to control display performance of CLOBs, etc. in Query Result view?

Whenever I attempt to query a table that contains LOBs (e.g. a CLOB or XMLTYPE), the lack of performance pretty much makes the "Query Result" view (from F9) unusable. Any time I attempt to scroll the results, SQL developer apparently continues to query the database for the additional characters to populate the view.
Resizing the columns containing the LOB to only a few characters almost solves the issue. Unfortunately, the size of the columns showing the LOBs apparently attempt to resize to the length of the LOB, making the column several pages long - and the same performance issue prevents resizing it smaller.
Ideally, there would be some way to resize a column to a given or even a predefined and small size, without having to drag the resize handle the entire width of the desired resize amount. Alternatively, there could be a user preference to never set default column widths above a given number of pixels or characters. Another option would be a user preference to disable the in-line display of LOB contents, displaying only and requiring a click on the "..." (or pencil icon) button to open the "View Value" dialog. Ideally, all 3 of these options could be implemented.
One crude work-around I'm using for now is to exclude the LOB columns from the results, requiring me to make secondary queries to see the LOB contents when necessary, and doesn't allow for scrolling through and viewing the LOB contents at all. Another work-around is to run the query as a script (F5) instead of a query (F9), and view the results in the "Script Output" view instead.
I'm currently using SQL Developer 2.1.0.63, but experienced this same issue with all previous versions, including 1.5.5.
Thanks!

I agree.
When I requested to auto-width the columns, I said to build in a maximum, but apparently they didn't.
I suggest you log 2 feature requests on the SQL Developer Exchange; 1 for the maximum width, 1 for the CLOB contents/performance. Like this others can vote too and add weight for future implementation (I will).
Have fun,
K.

Query Results not coming for SELECT * in sql developer 3.1.07

VERY FRUSTRATING to use sql developer.
In SQL DEVELOPER 3.1.07:
WHAT WORKS: select sequence# from v$archived_log
WHAT DOESN'T WORK : select * from v$archived_log
You've got to be kidding me.
I wish I can show a screenshot, but can't in this forum. Here's my description:
When I run the query, in the bottom frame for Query Results, it just says: Executing: select * from v$archived_log in 0 seconds.
Then there's no result grid.
WOw

>
This was when connected to a standby db that's in mount state
>
Is this a 'manual' standby db? Are you using Data Guard?
Post the results for what Gary ask of running the queries in sql*plus. If those queries give the same result then this is NOT a sql developer issue.
Review the following thread and post back with what information in it applies to your use case.
Re: V$ARCHIVED_LOG returns no rows on manual standby
If you are using Data Guard you may want to cross-post in that forum.

"Dead" Space before Query Results Display

We were required to use PL/SQL to create a report within HTMLDB. The report runs fairly quickly and is displayed as desired in the window with one exception. "Dead" space is always placed on the screen before the query results. In many cases, this space is only a couple of lines. In cases where the result set is a few hundred lines, there are a few hundred lines (usually a comparable number to the result set) before the query result. Therefore, the user sees an empty screen and doesn't always know to scroll down several times to reach the output. We are looking for a means to eliminate this leading space.

To perform the reqired sorting and add a checkbox to each section of the report, using PL/SQL embedded into the HTMLDB was the best method. Within the PL/SQL we used the htp.* commands to format the HTML. Unfortunately, this results in prgressively more empty lines before the actual report display with larger result sets.

Query Results: Retrieve All Rows?

I was looking for a feature that will allow me to choose to return "all records" to the Query Results window. The current behavior is to fetch 50 records at a time (e.g. fetch 50 records as you scroll through the results = s-l-o-w). What I'd like to do is "Retrieve All Rows" then use to the scroll bar to "smoothly" scroll to the last record. For example, the 8.0.6 version of Query Builder had this functionality and in SQL Developer 3.0, if I right-click on the results. I can choose to "Count Rows...", seems like this would be a perfect place to put a "Retrieve All Rows" option.

Hi,
My advice: do something only if there is a business case for it; satisfying your curiosity can get surprisingly expensive.
You have already read about using Run Statement to execute a SQL statement, then Ctrl-End to auto-scroll to the end. You can try the same for Run Script, but first you will probably need to increase the value of Tools|Preferences|Database|Worksheet|Max rows to print in a script. Of course, taking either of these approaches slows things down due to displaying output and scrolling. Same with SQL*Plus. And, as mentioned previously, Java memory management in SQL Developer can cause slow downs and hangs if the result set is large enough.
Here is a way to minimize that delay, avoid hangs, and get a more repeatable result:
1) Save some query to, say, C:\Temp\AllCustomers.sql. For example, "select * from customers;" or "select id from customers;".
2) Run it from a SQL Developer worksheet using Run Script (F5), or from the SQL*Plus command line, with a script like this:
set timing on
set termout off
spool C:\Temp\AllCustomers.lst
@C:\Temp\AllCustomers.sql
spool offEven then you will see that the timing results will vary. Maybe "select *" runs much slower than "select id" because the logical output lines are long and get wrapped into multiple physical output lines in the file. Minimize that by setting linesize to a longer value (but only in SQL*Plus -- it isn't supported in SQL Developer) and repeat the test to see. Maybe SQL*Plus runs it much faster than SQL Developer because one is a command line environment and the other a GUI tool with more overhead. Or maybe the SQL Developer JVM is near its size limit and lots of Java garbage collection is slowing it down. Simple question, complicated answer.
Regards,
Gary
SQL Developer Team
P.S.: And if by chance you are using a version of SQL Developer so old it does not include the output time in the query result tab's toolbar, using Run Script with set timing on is your only recourse.
Edited by: gggraham on Oct 27, 2011 4:54 PM

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

Managing a query result through several web pages

Hi,
I wonder what's the best way to manage a query result through several web
pages in the following context.
The query result is large and needs to be available through several web
pages. The user can scroll forward and backward through the pages.
One can :
- rerun the query at each web request and use random access
- run the query once for the first request, keep the pm and the query
somewhere (in a singleton class for example with a key in the HTTP
session) and use random access for handling the other requests (the
problems I see are to keep a connection for each user in this use case and
to decide when to close the previously mentioned objects)
- rerun the query at each web request, including in the filter a test on a
field and an ordering to start the results from the last one displayed
(being able to specify the maximum number of rows desired would be nice).
Thanks for any advice or suggestion.
Regards.

I think Frank's suggestion is probably the best tradeoff between memory
consumption (which would be high if you were to store the enire query
result in the session) and performance (which might be hurt if you
re-issue the query every time).
Note that Kodo 3.0 will provide a getObjectsById(Object[] ids) method
that should help in quickly instantiating a page of query results.
Query result limiting is currently under discussion for inclusion in the
JDO specification. We may have something for this in an upcoming Kodo
release (although not for 3.0).
In article <[email protected]>, Frank Riley wrote:
[email protected] (Patrice) wrote in
news:[email protected]:
Hi,
I wonder what's the best way to manage a query result through several
web pages in the following context.
The query result is large and needs to be available through several
web pages. The user can scroll forward and backward through the pages.
One can :
- rerun the query at each web request and use random access
- run the query once for the first request, keep the pm and the query
somewhere (in a singleton class for example with a key in the HTTP
session) and use random access for handling the other requests (the
problems I see are to keep a connection for each user in this use case
and to decide when to close the previously mentioned objects)
- rerun the query at each web request, including in the filter a test
on a field and an ordering to start the results from the last one
displayed (being able to specify the maximum number of rows desired
would be nice).For our paging code, we convert the query result to a list of object ids
(using pm.getObjectId()). We store this list on the session and only
instantiate the objects we need for a particular page (using
pm.getObjectById()). When a user does something that could possibly
change the query result, we rerun the query and replace the list on the
sesssion.--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

SQL*Developer 'Query Results' Not Displaying

I have just recently installed SQL*Developer v3.2.2 and after I run a SQL query the tab 'Query Result' tab is not displayed. I have tried to show this tab and to use the arrow keys at the bottom of the screen to display this screen but I cannot view the query results. I have used v1.5.1 in the past and know that it should display when after running a query and can be resized if required but I cannot seem to show it is v3.2.2

Hi,
Yes, I did install to a clean directory. I have even deleted all contents of the directory and re downloaded
the software again to the same directory but this did not work either it still remembered the original settings.Keep in mind there are two locations that an installation updates:
1. The SQL Developer installation directory (which you deleted).
2. The User-Related Information (in your "user home" directory), which is updated by the settings migration
Perhaps Jim meant you should also remove the user settings for the last SQL Developer version installed and possibly even avoid migrating the old 1.5.x settings when you first start SQL Developer after that. See the following forum thread, probably unrelated to your situation, but containing where to find the location of user-related information in the Help:
Re: IDE issue - Query Result grid is not selectable or scrollable
Hope this helps,
Gary
SQL Developer Team

Getting query results from a PL/SQL procedure

Hi! So, I’m a little stumped and I can’t seem to find the answer to what I believe is probably a simple question…
So, here goes… I have a big ol’ union query that I use to create a report on a page, it’s about 25k – not over the 32k limit, but fails to be able to compile every time (I always get a 400 – Bad Request error). I’m not sure why this is happening, but I can remove a union statement and it compiles just fine – so it has something to do with the size of the query. ANYWAY – I’ve resolved that I should put this bad boy into the database as a stored procedure and just call it from Apex, my problem is I can’t figure out quite how to do this with variables, etc.…
Instead of giving you my whole big query, I’ll use the emp table as the concept is the same:
Say we have a query that creates a report on a page:
select empno, ename, job, mgr, hiredate, sal, comm, deptno
from emp
where job = :P_JOB
and hiredate >= :P_HIREDATE;
How would I take this query, create it as a stored procedure on the db, pass the variables from Apex and return the query result set from the stored proc as a report?
I really appreciate any help on this!
Best,
Gilcrest

Hi Gilcrest,
You should create the query as a View and use the view name and the WHERE clause in the report's sql source.
Andy

Sending email using PL/SQL based on a query result

Hello all,
I want to create a procedure using PL/SQL, based on a query result.Here is the scenario:
I have multiple tables in Target and Source databases that I want to compare(not the whole table but queries on these tables) and if they differ, I want to shoot an email. I have some ideas how to implement this but not sure whether it is the best approach.
select Acct_id, total from SourceTableA
minus
select Acct_id, total from TargetTableA
select Acct_id, sum from SourceTableB
minus
select Acct_id, sum from TargetTableB
If the result of any of above queries > 0 then I want to shoot an email and want to repeat this procedure in the morning every day.
I know how to implement send_mail procedure using UTL_SMTP package and how to schedule tha job by dbms_job package. But I am not sure how to implement the result of minus query. In case if minus > 0 then I also want to send the name of tables in the email message where source and target tables are not same. Should i use cursor, variable or insert the result in a new table? any help would be highly appreciated. Thanks in advance.
Khan

Actually these queries are the part of our daily testing that we run everyday manually(after the scheduled ETL load) to see if there are any discrepencies between our datawarehouse tables and source tables. So instead of running these queries manually everyday we want to schedula a procedure that will shoot an email in case of any discrepency and indicate which tables have problems.

How can I get Numbers to return the first row in a group of VLOOKUP query results instead of last one?

I'm trying to query from one table (call it Table1) a batch of rows in another table (Table2) using VLOOKUP on a date specified in the first table (Table1). My problem is it's returning the last incident in Table2 of the requested date instead of the first incident. This really breaks the OFFSET scheme I'd like to use to collect the rest of the items for that date. Is there some way to compel VLOOKUP to return the first row of query results, not the last?
NOTE: I see I've asked this before, but forgot to go back and look at responses given. It's been a while and I've limped along until now with the way things were. I'm actually trying to delete this questions, so if you see it, ignore it. I suppose if someone can tell me real quick how to delete a stupid question, that might be helpful.

you cannot delete a post yourself. You can flag the post an request a moderator remove.

Warning Message in query result as 'Notification Number DBMAN 345'

Hi ,
I have a warning message while executing the query
'Diagnosis
Currently, it cannot be guaranteed that SIDs and master data exists for all characteristic attributes for the DataStore object to be read.
There is a restriction on a navigation attribute of the listed characteristic in the query. This filters all characteristic values of the master-data bearing characteristic for which there is not yet master data out of the result.
For performance reasons, this filtering is unavoidable.
System Response
Procedure
In case of doubt, find other restirctions directly on the characteristic values of the characteristics contained in the DataStore object.
Procedure for System Administration
Notification Number DBMAN 345 '
'i am getting this error because of cutomer exit variables on navigatioanl attributes of Omaterial'
I tried supressing it in RSRT.. but unable to find the message.
I tried debugging and assigning enhancement points in FM BAL_LOG_MSG_READ.. As it is standard function module its not suggestable to do..
can we creat custom FM ?? will it be called if we write code to supress warning message??
Please let me know how to use BADI'S in order to supress the error message that appearing in query result?
Thanks All.

Hi,
The warning is raised due to the following reasons:
- you have a selection in the filter of a navigation attribute
- in your DSO you do not use the option "SIDs Generation upon Activation"
If the option "SIDs Generation upon Activation" is not flagged,
you may get char.values for an Infoobject in the system not
having any SIDs. As a result you may see in the report less data as
expected.
For example we have Infoobject A with its Nav.attribute B
Infoobject A   Nav.attribute B
12             13   ->> has a SID in the X-table
11             10
9              13   ->> has no SID in the X-table
If you define a selection on B =13 in the query, you only get infoobject
A with key 12 displayed in the result, since only B =13 has a SID
in the relevant X-table.
The warning refers to this behaviour and cannot be avoided unless you:
   - flag the option in the ODS-settings
   - or remove the filter defined on 0MATERIAL__xxxx
Thanks,
Venkat

Saving query results to a flat file

Hello Experts!
We have a very specific issue on our current project and I would like to know if any of you have ever done something similar. We are taking query results from BW (after complex calculations, some based on SY-DATE) and saving them to flat files to transfer to a SQL database structure on the Enterprise Portal. From here, the portal team renders the information into more "static" dashboards that include mouse over features and even limited drilldown (i.e. no matter where a user clicks the report always drills down on profit center)
There are many reasons why the model is set up as such (mostly training of executive level end users), and even though it doesn't mesh with the idea that BW could do this work on its own, we have to work with what we have.
We have come up with 3 possible ways to save this data to flat files and hopefully someone can tell us which might be the most effective.
1.) Information Broadcasting. If we broadcast XML files to the portal, will the portals team be able to read that data into a SQL database? Is there another way to use broadcasting to create and send a flat file to specific location?
2.) RSCRM_BAPI. This transaction seems to not support texts.
3.) Open Hub. In order to get the open hub to work, we first have to save all of our query results to direct write data store objects using APD. (calculations based on current date, for example, would require daily full loads to the underlying data providers otherwise.)
What is the best way to accomplish this? Is information broadcasting capable of doing this?
Thanks!

Hi Adam,
Do you have to use flat files to load the information to a SQL database? (if so maybe someone else has a suggestion on which way would be the best).
I try to stay away from flat file uploads as there is a lot of manual work involved. May I suggest setting up a connection to your SQL table in the DBCON table and then writing a small abap program to push data into the SQL database (which you can automate).
1) Use APD to push data into a table within BW.
2) Go to transaction SM30 > table DBCON and setup a new entry specifying the conncection parameters to your SQL database.
3) In SE38 Write an ABAP program along the folloing lines (assuming the connection you set in DBCON is named conn1:
data: con_name like dbcon-con_name
con_name = 'conn1'.
exec sql.
set connection :con_name
endexec.
****have a select statement which reads data from your table which the data is saved from the APD into an internal table**********
****loop on the internal table and have a SQL insert statement to insert the records into the SQL table as below******
exec sql.
insert into <SQL TABLE> (column names seperated by ,)
values (column names of the internal table seperated by ,) if the internal table is named itab the columns have to be specified as :itab-column1
If you decide to take this approach you may find more info on DBCON and the process in sdn. Good Luck!
endexec.

Scroll to bottom of query results

Similar Messages

Maybe you are looking for