SQL Developer 4.0 Build MAIN-12.84 column width in data grid

A while ago I posted a thread about being unable to adjust the column width to "compress" everything on the screen to make the data more easily viewable. I just installed the latest build, and while it works slightly better, it still does not seem that there is any way of making the query results take up the least possible space. When you resize one column, it is affecting the size of other columns. Also, having to resize the columns for every query would be a massive hassle. Are there any plans to have an auto fit option that will fit to the least needed size that is necessary to display either the width of a heading and/or the data? The lack of this ability is why I am forced to stick to an old version of SQL Developer.

yup, already fixed for EA3 - you'll see the grids size to the space required, not to fill the screen. Just like you see in version 3.2.

Similar Messages

SQL Developer replacing Query Builder 6.0.7

Dear All,
We know SQL Developer 3.0 has a link to Query Builder from within it, but does it contain a similar structure as we saw in the old Query Builder 6.0.7 developed by Oracle long back?
The old Query Builder 6.0.7 could be used for editing and creating parameterised queries and generating formatted output, so just want to know if we can get the similar functionality using SQL Developer 3.0.
1. Whether SQL Developer 3.0 can create and edit queries by selecting data tables in Oracle?
2. Can it convert any old Query Builder queries (in .brw extension) to a format that can be run in SQL Developer 3.0?
I am about to download and install the SQL developer 3.0, but thought of asking here first and get some advice/views.
So, Please reply back with anything that might help me out.
With Regards,
Pamir

Yes thanks Jim...I realised that when I started to dig more into this.
Now I have downloaded and installed the software...currently am able to create, edit queries and do other stuff.
With Regards,
Pamir
Edited by: user651047 on 11-Aug-2011 06:56

SQL Developer 1.5.4.59.40 doesn't display any data or only nulls

Hi All,
I've got a problem with SQL Developer after I downloaded the latest version *1.5.4.59.40*. SQLDev doesn't display any data or displays only few lines of nulls within information tabs: Column, DATA, Constraints, Grants, Stats, triggers and so on....
Please see below screen shoots for details:
!http://www.emarcel.com/%7Eemarcelc/emarcel/SQLDEV1.gif!
And exception scratch:
!http://www.emarcel.com/%7Eemarcelc/emarcel/exception1.gif!
Note:
When I'm using an old version 1.5.0.51 everything works fine. But you know I would like to upgrade to the latest build.
Many Thanks for any help.
Cheers!!

The problem is solved by upgrading an oracle client_1 to 11g version,
Apparently these are the files which have caused the problem in old version of the oracle client (10.2.0..):
SQL Developer is using client's libs by default when it's installed for ex.:
jdbc.driver.home     /D:/oracle/product/10.2.0/client_1/
jdbc.library     /D:/oracle/product/10.2.0/client_1/jdbc/lib/ojdbc5.jar
AND:
orai18n.library     /D:/oracle/product/10.2.0/client_1/jlib/orai18n.jar
above libs are not compatible with the latest version of SQLDeveloper.
That's why the problem occurs.
Jim,
thanks for pointing me in the right direction. Cheers mate!!

Sql developer with compute function/ add total to column.

Hello experts i've been strugglin for a couple of hours on this. and im not sure if this is the forum i should be posting this but i could not found a forum directly related to sql developer.
I would like to use the compute function in sql developer but it does not appear to work can someone please point me in the right direction.
i followed this documentation
http://download.oracle.com/docs/cd/B19306_01/server.102/b14357/ch6.htm
but it does not seem to do the trick. I basically just would like to add a total at the end of my query ?...
can someone throw me a bone on this one.
Miguel

column DUMMY NOPRINT
compute sum of aamt on DUMMY
break on dummy
select a_fa_idoc, b_fr_idoc, a_amt, b_amt, (a_amt-b_amt)
from
   (SELECT a.fa_idoc a_fa_idoc, SUM(a.amt) a_amt from fwrinva a group by a.fa_idoc) fwarinva_summary
inner join
   (SELECT b.fr_idoc b_fr_idoc,   sum(b.amt) b_amt from fwrinvc b group by b.fr_idoc) fwrinvc_summary
   on( fwarinva_summary.a_fa_idoc = fwrinvc_summary.b_fr_idoc)
where (a_amt - b_amt) = 0;here is my query but it does not put a total on the end?

SQLDeveloper 1.5.1 (Build MAIN-5440) does not correctly export data.

At export of the data the script of the data insert is incorrectly generated. For example at export from "Tools"-->"Database Export" menu it generates following script:
Insert into "DIC_StructBlockType" (ID,"Name","Code") values ('[B@124e231' 'Center' '1');
instead of
Insert into "DIC_StructBlockType" (ID,"Name","Code") values ('30100000000111000000000000000100', 'Center', '1');
(where ID is RAW(16) or GUID)
I.e. wrong conversion of RAW(16) format and absence of commas in values section taking place
At export from data view of table i have
Insert into "DIC_StructBlockType" (ID,"Name","Code") values ('30100000000111000000000000000100' 'Center' '1');
without commas in values section instead of script above.
I know than in SQLDeveloper 1.5.0.52 (Build MAIN-52.03) insert script generation from table data view works normally (but not works in Database Export tool).
Whether there is a patch for this bug (in 1.5.1)?

The first issue seems like a previously unreported bug.
The second bug is because the values are (wrongfully) separated by the Preferences - Database - NLS Settings - Group Separator. Just change that to comma, and the Decimal Separator to something else.
Regards,
K.

SQL Developer 1.5.1 - Database Export - Exporting Column Comments

I have tried using the Database Export tool in SQL Developer 1.5.1 to export statements for "comment on column" but with no success. Is there a way to get these statements included in the DDL?
rasberry

When you select 'table' the comments are generated 'automatically'.
This is what you want?

SQL Developer 2.1 removes the stored password in SVN Application Data

Hello everybody
SQL Developer is a great Tool and I use it together with the SVN Versioning System. I also use TortoiseSVN on my Windows XP Operating System, that's why I found out that either the SQL Developer or its SVN Extension has a bug.
I have installed the latest SQL Developer 2.1.0.63.73 and the extension "*Versioning Support for Subversion* 11.1.1.2.36.55.30".
Both Tools the SVN Extension for SQL Developer and the TortoiseSVN save Authentification Data automatically in the same Folder "C:\Documents and Settings\UserXYZ\Application Data\Subversion\auth\svn.simple\" into some Files.
When I use TortoiseSVN, the password can be stored in those mentioned Files. That's very useful, so I don't have to enter my password every time I perform a SVN command. But when I later use SQL Developer and update/commit some file, the password will be removed from the above mentioned Files, even though my Password is stored in the SQL Developer's Subversion Navigator inside the Connection Setup of my Repository.
I would be happy to get some feedback from your point of view. Are there other people who have the same problem?
I turned already to google, but I haven't found a hint that it could be something you can configure in some properties.
Thanks in advance,
Ben

In the meantime I found the solution:
just add those two lines to the *%appdata%\Subversion\config* File
store-auth-creds = no
store-passwords = yes
It looks like the SVN Extension in SQL Developer has different Default Values for the properties than TortoiseSVN has.

Import problem SQL Developer 1.51 Build 5440

importing data using XLS file, the import wizard did not move to next step after selecting the required XLS file where as importing the same XLS data after converting into CSV format, it completes the process. although it is mentioned in the HELP that the DATAVIEW file be a XLS file but in the File Selection window XLS file type is not mentioned in the file type list.
Regards
Arshad Jamil

another thing that i forget to mentioned that after selecting the required XLS file the Sheet(s) selector did not show the sheets to be selected unless you expand the wizard window.
Thanks
Arshad

SQL-developer 4 EA unable to change the column sizes

when viewing data, it is not possible to change the column sizes like you do in a spreadsheet by sliding between the column-headers.
regards Karsten

when viewing data, it is not possible to change the column sizes like you do in a spreadsheet by sliding between the column-headers.
regards Karsten

SQL Developer 3.2 - Connection reset

Hi, I've installed SQL Developer 3.2 build MAIN-09.30 under Windows 7 64 bit and Client 11g 64 bit.
Wherever server I try to connect, when I click on a table I have the connection reset and it tries to fetch data with no success, i.e. the Results display show with the gauge moving and nothing more, while in backgroup I have a message box that suggets to reset the connection. If I stop task and choose some other thing, such as data, I can see tha data inside the table. Getting back to Columns, I have to click on refresh button but I don't see anything.
More, I have the following errors:
SEVERE     51     2348     oracle.dbtools.db.DBUtil     Avvertenza. Eccezione non gestita: Errore di I/O: Size Data Unit (SDU) mismatch.
SEVERE     50     22991     oracle.dbtools.db.DBUtil     Avvertenza. Eccezione non gestita: Errore di I/O: Size Data Unit (SDU) mismatch.
"Avvertenza. Eccezione non gestita: Errore di I/O" is italian for Warning: Unhandled exception: I/O Error
Can U help me please???
Thanks a lot
Edited by: user10660511 on 4-set-2012 7.58 - Added errors

Hi,
The case you describe is not familiar to me, but you may want to review this thread with a similar error:
java.sql.SQLRecoverableException Io exception Size Data Unit (SDU) mismatch
The comment there about a "recent JDBC driver upgrade to ojdbc6.jar" is interesting. I encountered a different error within the past couple weeks (can't recall exactly what), but noticed that the ojdbc6 jar files in 64-bit SQL Developer 3.2.09 and Instant Client's do not match. The SQL Developer jar is newer. Copying the one from the Instant Client (11.2.0.3) and replacing the SQL Developer version (supposedly 11.2.0.3 also) fixed whatever issue I faced. Comparing the manifest.mf files shows this:
ojdbc6.jar from SQLDeveloper 3.2.09.23 64-bit -> Repository-Id: JAVAVM_11.2.0.3.0_LINUX.X64_110829
ojdbc6.jar from Instant Client 11.2.0.3   64-bit -> Repository-Id: JAVAVM_11.2.0.4.0_LINUX_120621This is just my best guess at this point.
Let us know if this helps,
Gary
SQL Developer Team

Extension to Oracle SQL Developer

hi
could anyone share the details of how to do the following
i want to extend the sql developer such that whenever an update is performed in the data grid i.e. in the data tab i want to perform some custom action
could anyone help me how to start in order to achieve it.
Thanks in advance.

What's some custom action ?
Sure you don't just want a trigger?
K.

SQL Developer 1.0.0 on x86-64 (Suse Linux 10.1)

Has anyone tried running SQL Developer on a x86-64 machine ? I am use Suse Linux 10.1 and get the following error when I try to start SQL Developer -
Exception in thread "main" java.lang.NoClassDefFoundError: java/lang/StringBuilder
at oracle.ide.performance.PerformanceHandler.getPropertyObject(PerformanceHandler.java:41)
at oracle.ide.performance.PerformanceHandler.getFormatter(PerformanceHandler.java:31)
at oracle.ide.performance.PerformanceHandler.<init>(PerformanceHandler.java:25)
at oracle.ide.performance.PerformanceLogger.<init>(PerformanceLogger.java:66)
at oracle.ide.performance.PerformanceLogger.get(PerformanceLogger.java:94)
at oracle.ideimpl.Main.main(Main.java:21)
Thanks in advance !

Here are the JVM details:
echo $JAVA_HOME gives:
/usr/lib64/jvm/java
java -version gives the following:
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_07-b03, mixed mode)
I did the following after deleting $HOME/.sqldeveloper_jdk file:
./sqldeveloper
Oracle SQL Developer 1.0
Copyright (c) 2005 Oracle Corporation. All Rights Reserved.
Unable to find configuration file: jdk.conf
Type the full pathname of a J2SE installation (or Ctrl-C to quit), the path will be stored in ~/.sqldeveloper_jdk
Entered /usr/lib64/jvm/java for the java path
Now I get the following error:
/usr/lib64/jvm/java
Working directory is /home/venkat-work/sqldeveloper/jdev/bin
Error: hotspot VM not supported
Error: SQL Developer can't recognize the JDK version

GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

Folks,
I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
via a download fro the GeoRaptor website.
No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
We are still looking for people to:
1. Provide translations of the English dialog menus etc.
2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
you have found out all its functionality and quirks, contact us and offer to write a few pages of
documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
make screen captures and annotate with text.
3. Conduct beta testing.
Here are the things that are in the new release.
New functionality:
Overhaul of Validation Functionality.
1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
   NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
   to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
4. Main validation table allows:
   a. Sorting (click on column header) and
   b. Filtering.
   c. Copying to Clipboard via right mouse click sub menu of:
      - Geometry's SDO_ELEM_INFO array constructor.
      - SDO_GEOMETRY constructor
      - Error + validation string.
   d. Access to Draw/Zoom functions which were previously buttons.
   e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
      it can process - along with the ring / element that is host to the error (if it can) - and displays
      them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
      The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
   f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
   g. Table now has only one primary key column, and has a separate error column holding the actual error code.
   h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
   i. Optimisations added to improve performance for large error lists.
5. Functionality now has its own validation layer that is automatically added to the correct view.
   Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
Improved Rendering Options.
1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
2. Marking of SDO_GEOMETRY objects overhauled.
   - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
     option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
     could be shown as: <25> or {x,y} or <25> {x,y}
   - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
   - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
     edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
   - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
   rather than previously fixed markers.
4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
5. Positioning of the arrow for linestring/polygons has extra options:
   * NONE
   * START    - All segments of a line have the arrow positioned at the start
   * MIDDLE   - All segments of a line have the arrow positioning in the middle.
   * END      - All segments of a line have the arrow positioning in the END.
   * END_ONLY - Only the last segment has an arrow and at its end.
ScaleBar.
1. A new graphic ScaleBar option has been added for the map of each view.
   For geographic/geodetic SRIDs distances are currently shown in meters;
   For all SRIDs an attempt is made to "adapt" the scaleBar units depending
   on the zoom level. So, if you zoom right in you might get the distance shown
   as mm, and as you zoom out, cm/m/km as appropriate.
2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
   to the map's right most status bar element.
3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
   click menu.
Export Capabilities.
1. The ability to export a selection from a result set table (ie result of
   executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
   adds TAB file "wrapper" over SHP) has been added.
2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
   added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
   automatically adds a field that holds a unique row number.
3. When exporting to KML:
   * one can optionally export attributes.
   * Web sensitive characters < > & etc for KML export are replaced with > < & etc.
   * If a column in the SELECTION or table/view/Mview equals "name" then its value is
     written to the KML tag <name> and not to the list of associated attributes.
     - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
   in GeoTools is corrected (working with GeoTools community to fix).
6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
   Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
7. Export directory is remembered between sessions in case a user uses a standard export directory.
8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
   Example:
   SELECT a.geom.sdo_point as point
     FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
             FROM DUAL) a;
   SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
     FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
   than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
   the number of points exported, and multipoints skipped will be displayed.
10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
    However, this does not currently apply to the associated DBASE records.
11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
    Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
    to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
    Please read the Oracle documentation on how to project your data is this is necessary. An example is:
    SELECT OBJECTID,
           CODIGO as name,
           NOME as description,
           MI_STYLE,
           SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
      FROM MUB.REGIONAL;
13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
    circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
    to use this.
Miscellaneous.
1. Selection View - Measurement has been modified so that the final result only shows those geometry
   types that were actually measured.
2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
   Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
   and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
   in map display): everything within that distance is returned.
5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
   a preference.
6. New View Menu options to switch all layers on/off
7. Tools/Preferences/GeoRaptor layout has been improved.
8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
   has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
   what the layer is set to being.
9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
   and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
   In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
   right mouse click menu.
10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
    has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
    index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
    which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
Some Bug Fixes.
* Error in manage metadata related to getting metadata across all schemas
* Bug with no display of rowid in Identify results fixed;
* Some fixes relating to where clause application in geometry validation.
* Fixes bug with scrollbars on view/layer tree not working.
* Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
schema of the current user, as it could happen that a user opens the tree for another schema that
has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
* Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
in a recordset. Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row. It appears
that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
cells in the row.
* Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
* Column based colouring of markers fixed
* Bunch of performance improvements.
* Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
If you want to help with testing, contact us at our website.
My thanks for help in this release to:
1. John O'Toole
2. Holger Labe
3. Sandro Costa
4. Marco Giana
5. Luc van Linden
6. Pieter Minnaar
7. Warwick Wilson
8. Jody Garnett (GeoTools bug issues)
Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
expressing ideas for future functionality and integration opportunities.
regards
Simon
Edited by: sgreener on Jun 12, 2011 2:15 PM

Thank you for this.
I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
I have stumbled to few bugs:
1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
I found this because in my language settings , is the decimal operators
2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
- if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

SQL Developer 3.2.09 and excess memory usage

This is really something that will ultimately end up as a bug-fix request, I'm thinking, but I was wondering if anyone else is seeing the same thing, before I report it.
We're using SQL Developer 3.2.09 in a Citrix environment, and we're finding that it's using up an inordinate amount of memory, causing performance problems for anyone else with applications open on the server. We haven't seen any patterns so far ... like if it's a side-effect of having the tool open for long periods of time (memory leak), or if certain activities within the tool are prone to using up too much memory.
Has anyone else experienced the same thing when running SQL Developer on their desktop, or in Citrix? And have you been able to tune it at all?
Thanks,
--=Chuck

SQL Developer is java based and relies on the jvm's memory management.
I'm not aware of any memory leaks as such, but memory tends not to be returned to the system.
Queries which return large return sets tend to use a lot of memory (SQL Developer has to build a java table containing all the results for display).
You can restrict the maximum memory allocated by modifying settings in in <sqldeveloper>\ide\bin\ide.conf
The defaults are -
AddVMOption -Xmx640M
AddVMOption -Xms128M

SQL Developer Data Modeler -Editing the Legend

Hi,
I have installed SQL DEVELOPER Version- 3.0.04. I am creating the data modeler diagrams(Relational and Logical) using the SQL Data Modeler.I would like to know whether the following features are available in this version or the latest version of SQL DEVELOPER.
1) Remove the existing legend attributes (Say:Author,Created on,Changed By etc) for both relational and logical diagrams.
2)Add new attribute to the Legend .(Say: A description for the Barker notation used in ERDs .)
Regards
Anupam
Thanks in Advance
Edited by: 898511 on Nov 22, 2011 3:34 AM

I answered my own question. In case anyone doesn't already know. Easy enought...
right click on the diagram
-> unselect "Auto Route"

SQL Developer 4.0 Build MAIN-12.84 column width in data grid

Similar Messages

Maybe you are looking for