Question

I am using DBVisualizer 8.0.6 and when I run a simply query like....

select * from table

It only shows the first 1000 rows and then stops the query and displays in the bottom left corner... "Number of rows limited by maxrows"

How do I change this #? I'm writing a query which needs to export a little over 1000 rows but dbvisualizer has this set limit...

I tried something like @set maxrows 2000 then commit then run my query. Still returns only 1000 rows. This is for an Oracle table.

Was it helpful?

Solution

There is a box in SQL Commander labeled Max Rows. Set it to -1 for the complete result set.

Max Rows

OTHER TIPS

Or you could just export directly to a file. This will allow to export many more rows than the DBVisualizer GUI can show you. When having to export a few million records (should you ever need that), this is quite useful.

Simply do something like this in your SQL Commander:

@export on;
@export set Filename="d:\temp\export" format="CSV" DecimalNumberFormat="00000000000" CsvRowDelimiter="\r\n" CsvIncludeColumnHeader="false";

SELECT YOURFIELD FROM YOURTABLE WHERE SOMEFIELD = AFILTERVALUE;

You can find more about this (and the various parameters) here: http://www.dbvis.com/products/dbvis/doc/7.1/doc/ug/sqlCommander/sqlCommander.html#mozTocId448386

so apparently you need to have DBVisualizer Personal edition to set the maxrows, which the free edition doesn't support. You can get a free trial though. Then you can run something like...

@set maxrows 2000; 
select * from table;

If anyone knows how to do this in the free version please feel free to comment, thanks.

From this page, it looks as though the maximum number of rows returned initially is specified within the Tool Properties dialog, on the General Settings tab, on the Table Data node in the Max Rows at First Display property.

select * from table where rownum < 10 would return 9 records for oracle.

But It varies db to db .

Sql server uses select top N fieldName from table.

For MySQL syntax changes as SELECT *FROM table LIMIT N

Maybe Some others use take , skip, etc... So using dbvisualizer , and its setting in the accepted answer is logical for cross db users. It doesn't bother you by varied sql syntax.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top