new feature SQL History is more or less useless

HenrikM

Hi,

I am the only one, who has a bad experience using the new feature SQL History in SQL Prompt in SSMS.

1. Opening SQL History takes 1-2 minutes and SSMS is completely frozen while opening the SQL History tab
2. Searching for keywords etc. in SQL History freezes SSMS and often crashes SSMS, forcing you kill the SSMS process and opening SSMS again.

Come on Redgate, You should be able to do better..

Regards
Henrik Munch

dkim1999

Hi Henrik,

Thank you for reaching out and I apologize that you are running into issues with SQL Prompt.

When SSMS crashes, is there an error message accompanied with it?

In addition, are there any errors within the SQL Prompt log files?

Thank you!

David K.

Product Support Engineer

HenrikM

When I say crashes SSMS I mean that SSMS becomes unresponsive and I have to kill the SSMS process.. 
Sometimes maybe if I wait several minutes (3+ minutes) SSMS will become responsive again.

I have checked the logs and in the sqlprompt-sqlhistory*.logs found this Exception

2022-12-05 12:45:10.003 +01:00 [Information] Logging level set to 'Information'

2022-12-05 12:45:10.195 +01:00 [Information] Started successfully with identifier '*****************************'

2022-12-05 12:45:10.266 +01:00 [Error] Error processing operation

System.NullReferenceException: Object reference not set to an instance of an object.

   at RedGate.SqlPrompt.SqlHistory.Storage.StoreInitializer.Create()

   at RedGate.SqlPrompt.SqlHistory.Storage.Commands.CommandStore.AddContentsRevision(Guid queryIdentity, String name, String path, String contents, SqlHistoryConnection connection, SaveReason saveReason)

   at RedGate.SqlPrompt.SqlHistory.Server.Commands.CommandProcessor.StoreContentsRevision(RevisionMessage message)

   at RedGate.SqlPrompt.SqlHistory.Server.Commands.CommandProcessor.ProcessCommand(CommandOperationType commandOperationType, ICommandMessage message)

   at RedGate.SqlPrompt.SqlHistory.Server.OperationQueue.ProcessQueue(Object sender, DoWorkEventArgs e)

2022-12-05 12:45:14.020 +01:00 [Information] [Startup status] Size on disk (bytes) = 377958400, Number of queries = 46308, Number of revisions = 50798, Highest revisions per query = 102, Longest contents (characters) = 4781898

dkim1999

Hi Henrik,

Thank you for sharing the logs.

It appears that this is a known issue by the development team and they are actively looking into a fix.

I can update you once a fix is released.

Kind Regards,

David K.

Product Support Engineer

TJSmith

Mine doesn't crash, but it's certainly much slower (some seconds vs instantaneous) to open than the old tab history. I came here to see what others were saying about the feature, since the old tab history was one of my favorite tools.

I'd be less bent out of shape about my cheese being moved/changed if it didn't feel like Bringing Out the Big Guns whenever I want to break out one of my most frequently used features.

jeppe

My Tab History was actually starting to throw exceptions left and right. It was becoming unusable.

SQL History seems to be working pretty well. It is not instantaneous in its search, but it is reasonably fast considering how much it is indexing.

alphonseg

I'm seeing the same issues of SSMS freezing and tab history slow.

PaulKahl

This is still a problem as of 2023-06-29. SQL History takes incredibly long to load as a whole, and each file you click on takes longer to load, in addition to searches taking even longer. And all of these things lock SQL while loading.

File this under "Not fixed".

PetteriY

Seems to be a problem still, as I did run to this today. SSMS goes totally unresponsive, and only end task will work. As next time this happens again, SSMS is totally out of reach. How to bypass history opening?

PetteriY

To prevent this SSMS stuck loop, remove file SqlHistory.db from user "\AppData\Local\Red Gate\SQL Prompt {version}" folder. SQL Prompt will generate a new empty one, and you can continue with SSMS.

As that is SQLLite database, you could also use DB Browser for SQLite to find the problem in the history and try to remove it.