SQL History always emtpy or disabled

When I started evaluating SQL developer, I used the sql history as a very usefull feature. One day, I noticed the SQl history does not log any longer any new SQL commands. To resolve this problem, I tried it with a clear history. From that time on the history is empty and the button disabled. What went wrong? I already checked the preferences.
Client: WinXP prof., SQL developer 1.0.0.15.57, connected Db from 8.x to 10.x

Seeing as sqlplus worksheet has used F5 for years and saves history, actually, it kind of does. I don't understand why they would intentionally counter the behavior of the long-utilized tool this functionality replaces (and that some of us still have to use on a regular basis). It seems like F9 and F5 should be swapped.
My 2 cents.
FYI, I found this thread because I was having the same problem. :)

Similar Messages

SQL CPU always on top at 10:00 am, no jobs are execute at that time...any tool that helps me to find the issue?

Hi everyone,since one month ago, my sql server 2008 has been experimented that something makes that my cpu server always be on 100% at 10:00 am , and even sometimes have crashed the server because of this,i have no executions jobs programmed at that time,
ran sql history jobs to see if i missed some job, but not even one job seems to be executed at that time, also there is no antivirus or windows update programmed at time
Does any one can recommend me a tool that not be the sql profiler , that we can use to be on monitoring at that time and tried or catch what makes that the sql cpu go to 100%, this happens all days at the same time.
Thanks for your time and if there is any way that i can give you more information please tellme
----More Information
Well basically the sql server its a virtual server, at 10:00 am the sql works slower than usually, the ti support that is monitoring the virtual machine , see that cpu starts to raise at that time (10:00 am) and
usually takes 1-2 minutes to back to normally, i had a back up BD log and differencial at that casually was execute at time, i had to change the time and now does not affect at 10:00, when i had this backups the server crashes, because the cpu was not enough,
now i moved the job (back up log adn diff) and the server dont crashes anymore, but still be something at 10:00 that make the cpu raises to the top. by test we disabled mcaffe and even with mcaffe down the server still having the same issue.
elijos3110

Elijos,
What do task manager or ProcessExplorer say at 10:00 AM? Could be an anti-virus program or something.
Hi, thanks for your time, Well
basically the sql server its a virtual server, at 10:00 am the sql works slower than usually, the ti support that is monitoring the virtual machine , see that cpu starts to raise at that time (10:00 am) and usually takes 1-2 minutes to back to normally, i
had a back up BD log and differencial at that casually was execute at time, i had to change the time and now does not affect at 10:00, when i had this backups the server crashes, because the cpu was not enough, now i moved the job (back up log adn diff) and
the server dont crashes anymore, but still be something at 10:00 that make the cpu raises to the top. by test we disabled mcaffe and even with mcaffe down the server still having the same issue.
elijos3110
elijos3110

SQL Developer SQL History no longer working 3.2.20.09.87

Hi guys, The SQL History (F8) option has started to no longer work within my copy of OSD.
it was working at one point but has gone away.
I have confirmed that "Enable Local History" is enabled and has been set for 30 days history and 50 max revisions
I have confirmed that I still have a SqlHistory.xml file located in my user\operator\AppData\Roaming\SQL Developer\ directory with entries in it (6933 rows of data)
This started to happen after I started to play with the Garbage Collection settings to reduce the memory footprint of OSD.
I have since restored all of my backed up delivered settings, rebooted and the SQL History will not show up again.
My snippets and custom reports are working and I can still see the log detail where I used to see log and sql history options at the bottom of OSD.
I'm using Windows 7 and can provide an OSD dump if it helps.
Thanks...
Tom
Edited by: ERPDude on Mar 6, 2013 10:03 AM

Hi Tom,
Be careful about which preference settings relate to the functionality in question.
1. Tools > Preferences > Environment > Local History > Enable relates to a worksheet's History tab when you File > Open
2. Tools > Preferences > Database > Worksheet > SQL History Limit relates to View > SQL History pane.
You do not say how you backed up and restored your settings during all your experimentation, but let's assume whatever you did was valid. Whenever some UI component mysteriously disappears, one thing I always check (usually just delete) is the windowinglayout.xml in system3.2.20.09.87\o.ide.11.1.1.4.37.59.48 of my user settings.
For example, I can use the SQL History pane's tab context menu to Float it, then adjust it's size by dragging it's edges down to a grey square a few pixels wide/high. Close SQL Developer, reopen, View > SQL History. Darn! Where did it go?
Hope this helps,
Gary

Quantity of SQL History shrinking

I've noticed since about Dec. 2006 or Jan. 2007 that the quantity of SQL History kept has varied greatly and generally shrunk. In the last five days it has shrunk from 21 days to 10 days. I currently only have 47 entries in SQL History. I estimate that I execute a minimum of 20 unique queries every business day, so a significant number of my queries over the last 10 days are missing from SQL History.
In addition, today I'm noticing that I only have entries from a single database connection in SQL History. I have executed queries against two database connections today and at least 4 others over the last week. But only one of those database connections is reflected.
I've counted the entries in "SqlHistory.xml" and it matches the number of entries I see in the SQL History dialog.
Any ideas on what is happening to my SQL History? I am aware of the bug that can wipe out all of the SQL History prior to the time when a second instance of SQL Developer is opened. In this case though, I still have 10 days of history and history for all but one database connection is missing.
SQL Developer 1.1.2.25
Oracle 10g Enterprise Edition 10.2.0.2.0 - 64bit (all databases I access are the same version)
Java 1.5.0_05
Windows XP Pro SP2
132gb free space on the drive which has both Windows installed and SQL Developer.
Pentium 4 3GHz
2GB Ram

Bill,
I assume this happened on htmldb.oracle.com. I bet one of our (necessary) cleanup jobs kicked in and purged some old statements.
Sergio

SQL History - returning wrong statement if history is sorted

I have searched the forum and not seen anything on this, but I have been getting the wrong SQL statement returned when I select Append/Replace.
I have statements going back to 12-Jan-06 (using 804 since 13-Jan-06, 796 since 12-Jan-06 and 715 last year), so I don't know if I have hit the aging limit or not (I think I counted 221 entries).
It seems to me that it works out the cursor position and then returns that statement number from the history - independently of resorting the history.
For example, if I sort from oldest to newest (based on timestamp) and then select the bottom statement (displays as newest) and Replace, I get the oldest statement in the worksheet. If I select the top statement (displays as oldest) and Replace, I get the newest statement in the worksheet.
This is further complicated by the fact that sorting on the Timestamp is doing an alpha-numeric sort, rather than a date sort. When sorting from oldest to newest, the bottom three timestamps are (in "oldest to newest" order) are:
1/23/06 10:58 AM
1/23/06 9:21 AM
1/23/06 9:31 AM
If I then remove the sorting, the statement returned is the correct one.

It was great to get the fix for the SQL History returning the right statement if sorted (we got it in v1184).
However v1215 still does a text sort on the TimeStamp column rather than a date sort, so 2PM comes before 9AM, etc.
Also, where is the format for the TimeStamp column coming from? As someone who doesn't live in the US and thinks that days should come before months in date formats (ie DD-Mon-YYYY), I am frustrated by yet another product that uses MM/DD/YY, despite my best efforts at telling it otherwise.

Backup Sharepoint 2013 Farm with SQL 2012 "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 Farm with SQL 2012 "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find confirmation anywhere.
Regards,
John

Per this thread
http://social.technet.microsoft.com/Forums/en-US/0c047737-4733-4ad5-a24d-3e6e6ff42f70/dpm-2012-sp1-and-sharepoint-2013-on-a-sql-2012-alwayson-ag?forum=dpmsharepointbackup, no it does not look like this is supported.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL Server Agent(Agent XPs disabled)

I've an issue with SQL Server Agent which is disabled and I'm trying to enable but it won't work.
I've used following steps. Can someone guide me? Thank you reading and helping me.
STEP.1 EXEC SP_CONFIGURE 'Agent XPs'
STEP.2 EXEC SP_CONFIGURE 'show advanced options',1
GO RECONFIGURE GO EXEC SP_CONFIGURE 'show advanced options' STEP.3 EXEC SP_CONFIGURE 'Agent XPs',1 GO RECONFIGURE

Hello Neha,
I tried all steps as you mentioned but still not help..
Here is following details for SqlAgent log,...
2014-01-09 10:06:38 - ? [100] Microsoft SQLServerAgent version 9.00.5000.00 ((Unknown) unicode retail build) : Process ID 304
2014-01-09 10:06:38 - ? [101] SQL Server Web version 9.00.5057 (0 connection limit)
2014-01-09 10:06:38 - ? [102] SQL Server ODBC driver version 9.00.5000
2014-01-09 10:06:38 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
2014-01-09 10:06:38 - ? [310] 8 processor(s) and 24575 MB RAM detected
2014-01-09 10:06:38 - ? [339] Local computer is HRWEB01 running Windows NT 5.2 (3790) Service Pack 2
2014-01-09 10:06:38 - ? [432] There are 11 subsystems in the subsystems cache
2014-01-09 10:06:38 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent
2014-01-09 10:06:38 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2014-01-09 10:06:38 - ! [298] SQLServer Error: 22022, Usage: EXECUTE xp_sqlagent_notify <operation type>, <job id>, <schedule id>, <alert id>, <action type> [, <login name>] [, <error flag>] [SQLSTATE 42000]
2014-01-09 10:06:38 - ! [442] ConnConnectAndSetCryptoForXpstar failed (0).
2014-01-09 10:06:39 - ? [098] SQLServerAgent terminated (normally)

SQL History and timestamp order

Hi, I have SQL Developer 12.84 (4.0.0.12).
Sql history forces MM/DD/RR format in Timestamp instead of NLS format: DD.MM.YYYY HH24:MI:SS.
As a consequence the sort order fails.
Played with C:\Users\<user>\AppData\Roaming\SQL Developer\SqlHistory files but each new entry ignores manual date changes and writes timestamp in strange format.
Any idea?

Already identified by developer team as:
Bug 17740406 - SQL HISTORY TIMESTAMP NOT SORTED AS DATE FOR NON-US LOCALES
Info based on: https://forums.oracle.com/thread/2601066 (why new thread)
This is important drawback in SQL Developer 4 for non US users. BTW, still not fixed in build 13.30 (4.0.0.13)

EA3 - SQL History window refresh problem

Hi, I have noticed that version 1.2 (possibly farther back) up to and including 1.5 EA3 have a issue with refreshing the SQL history window in a special scenario.
If the tab is completely undocked from SQL developer and then expanded across two monitors, as I scroll down the parts of the data rows on the non-primary monitor are not refreshed and become jagged.
I am running SQL developer on Win XP SP2 with whatever version of Java came with EA3.

Thanks, that seemed to work. It looks like Java is painting the grid in two parts now, with the non-default monitor side being second, but at least it repaints.
As far as a default, I did already have the following option in the config file:
AddVMOption -Dsun.java2d.ddoffscreen=false
I don't what difference the -J option makes but that's what I had. Thanks again.

EA3/EA2 - SQL History Timestamp column

The formatting of the Timestamp column in the SQL History now uses the NLS Timestamp Format (yay!), but unfortunately does not cope with the seconds component of the format:
NLS Timestamp Format is DD-Mon-YYYY HH24:MI:SSXFF
Timestamp column in the SQL History displays as 25-Feb-2008 15:03:.
I assume from what has previously shown in the SQL History timestamp column (2/25/08 3:03 PM) that we do not record seconds in the SQL History timestamp. I don't really have a problem with that, but can we please trim the second and sub-second components from the format?
theFurryOne

Just to add, this specific problem has been fixed. Hiding of sec/mill-sec information is handled by ignoring 'S/F', '.X', ':X' fields . But keeping the bug open so that a more generic fix is made which will handle symbols like '#SSXFF' in time field.

EA1 - SQL History Timestamp format

Feature Request "SQL History Timestamp - NLS Date format" (Use the current NLS Date or Timestamp Format preference for formatting the Timestamp displayed in the SQL History window) is listed as Scheduled for 1.5 but has not been included.

Rakesh,
Thanks for the update. I assumed that it hadn't been done yet, as it is using a different "default" NLS date format from the results tab, which also is not picking up the NLS date format preference.

SQL History not sorting by timestamp; new v4 TS format ?

I was worried that my SQL History was not accumulating post upgrade, as it did not appear as I expected.
I typically sort it by descending timestamp, but I'm finding that since installing the 4.0 production version that a different timestamp format on SQL History has taken hold, ignoring the NLS settings that I put in my preferences (which were not the default ones by the way for my territory and language, by the way).
I migrated all my settings from the previous installation I had ...sqldev4 ea3. previous migrations from v3 to v4 ea1 to v4 ea2 to v4 ea3 never disrupted my SQL History.
Now my recent entries are buried in the SQL History and won't show on top anymore, and the sorting by timestamp seems erratic making it impossible to see a chronological order of SQLs executed before and after the migration.
Is there a control for formatting the SQL History timestamps or do I need to go spelunking through xml files to alter a setting ?
Curiously,
Steve

A timestamp found inside one of my older "history.xml" files looks like this:
<timestamp><![CDATA[12/11/13 2:18 PM]]></timestamp>
A newer one looks like this:
<timestamp><![CDATA[12/17/13 20:54]]></timestamp>
It would probably give Xquery fits reconciling the different formats, sorting, eliminating older SQLs in the history according to one's preferences inside SQL Developer 4, etc.
I'm going back to the last early adopter release just to preserve history and sequence until the tool makers resolve the timestamp and the weird sort order problem.

BUG in purging sql history entries...

Hi folks,
I am using 1.5 and have been using also the versions before. Great that the sql-history window is dockable now, much more useful this way...But...
it is still totally ununderstanble to me, with wich rule entries in the sql-history are being purged. I just open the sqldev again, and see almost entries removed. When does that happen, is it possible to configure this setting?

Hi guys,
yes, I mean an arbitrary purge. Like, you finish your job for today, close sqldev, go home, come back the next day and only 4 or 5 entries of the log are still there... (???)
No problem, I have full understanding for an algorithm for purging entries older than two or four days, or something similar. But until now, there was no repliccable rule in that process!
By the way, I cannot find a sqlhistory.xml in my install-directory...

SQL Developer 1.5.3 SQL History Functions gray'd out

When I press F8 to list my SQL History I see plenty of queries but I cannot D&D or use andy of the replace, append features to insert the prior run.

Check if you opened a sql file and didn't select a connection for it from RHS connection selector in worksheet.
-Raghu

Sql 2012 always on setup

I got a sql 2012 always on setup between 2 standalone servers in 2 different locations.
I do not understand why I need cluster manager managing the 2 nodes.
I have cluster manager but there is no shared disks. there are 2 nodes under cluster manager and one cluster name.
what would be the different between the cluster name here and the availability group listener name in sql 2012? they are both different names

Read those articles
https://www.microsoftvirtualacademy.com/tracks/mission-critical-confidence-using-microsoft-sql-server-2012
http://www.sqlservercentral.com/articles/FCI/92196/
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SQL History always emtpy or disabled

Similar Messages

Maybe you are looking for