Why Oracle SQL Developer is so slow when open a big script? - oracle-sqldeveloper

I have a script which has more than 15,000 lines. it will take around 90 seconds to open in Oracle SQL Developer. But when opening it in DBeaver or Navicat, it can be opened immediately. why is this happening? How to solve? Thanks.

Related

Does Oracle SQL Developer refresh when you launch it?

I've just run a couple of queries where I forgot to click on the blue 'refresh' button when I launched Oracle SQL Developer.
But I was wondering whether it actually refreshes anyway, when you actually launch it?
Short answer: 'no.'
But first, let's share with folks with the 'blue refresh button' you mention in your question.
What does this button do?
It re-executes the query that the resultset is tied to, in this case
select * from employees
When you restart/re-open SQL Developer it does not even connect to any databases, much less re-execute any queries automatically.
What you might see is a .SQL file re-opened as you had it open when you closed the application from your last session. But no database work will happen until you hit the 'Connect' button.
Disclaimer: I work for Oracle and am the product manager for SQL Developer.

Experiencing GUI delays in Oracle SQL Developer

I use the Data Import Wizard (DIW) for file loading. And lately, simply right clicking on a table and then selecting the DIW option to bring up the wizard, I experience a 1-2 minute lag before the GUI dialog box even comes up. Furthermore, as I progress thru the steps of the DIW GUI, each step will delay 1-2 minutes before moving on to the next. So all together, using the DIW can typically take me > 10 min.
What could be causing this and how might I remedy the issue?
I'm using Oracle SQL Dev version: 18.4.0.376
Regards,
rhelm
Finally was able to update to the current v19.2 and no longer experience any delays.

Can I restore recent query output in Oracle SQL Developer?

I have a large query I am running in Oracle SQL Developer. The query seemed to run successfully and then I made the mistake of hitting count rows and it froze. I had to terminate the program in the task manager. I have been searching online and I have seen a lot about how unsaved scripts can be recovered using history, but I dont see anything about restoring the query result. Is it cashed anywhere so I dont have to run the query all over again?
Any help is greatly appreciated.
If you are using PL/SQL Developer, then you need to press CTRL+E. You can find Recent Executed Quer

Working on .mdf and .sdf at the same time

Is it possible to open .mdf and .sdf database types in the same Sql Sever Management Studio session?
I have tried, and it obviously did not work. I am guessing I either have something configured wrong or they are not compatible. I can open each up separately of course using the appropriate database provider when opening SSMS.
I was just hoping there was a way or maybe some other MS tool, plug in or app I don't have that will allow them to work together.
I was hoping to use TSQL to populate the Compact Db but it appears I need to code up an app or something to do this. Any suggestions on porting data to compact?
Use my free Visual Studio add-in "SQL Server Compact Toolbox", lets you move data and schema from SQL Server to Compact in a single click

How to save the state(all open windows and tabs)?

is it possible to save the current state(all open windows, tabs, connections, files, etc...), shut down SQL Developer, restart it some other day and resume work where you left?
Yes, I've tried it with my SQL Developer Version 4.0.3.16 Build MAIN-16.84
Every time you close SQL Developer while some tabs opened, it will opened those tabs again when you open SQL Developer again
However, SQL Developer won't remember the connections you used to execute those SQLs. So when you try to execute those SQLs, you will prompted to choose the connection where the SQL will be executed
nb : you can also open recent files by using Navigate -> Go To Recent Files
Just to add to nobodykid's answer: It seems to me that open tabs with queries in are not displayed at next session unless they are stored to a file on disk explicitly by the user.
In other words, if you close SQL developer and you do not save your tabs as files on disk explicitly, the tabs will not be recovered upon restart.