SQL History Search Not working

prozach99

When I try to search SQL History it doesn't return anything. I see the below error in the logs. I'm able to query the database directly using db browser, but i'd prefer to search SQL history from the SQL prompt interface.

2024-11-13 09:44:56.462 -05:00 [Information] Trimming history...

2024-11-13 09:44:56.581 -05:00 [Information] History trimming complete (time taken = 00:00:00.1200647)

2024-11-13 09:44:57.903 -05:00 [Information] [Startup status] Size on disk (bytes) = 81915904, Number of queries = 4460, Number of revisions = 11218, Highest revisions per query = 209, Longest contents (characters) = 907601

2024-11-13 09:44:57.996 -05:00 [Information] Indexing SQL History to C:\Users\zgelnett\OneDrive\Documents\WorkStuff\Settings\SSMS\SQL Prompt\SqlHistoryIndex...

2024-11-13 09:44:58.086 -05:00 [Error] Error indexing database

System.FormatException: Additional non-parsable characters are at the end of the string.

   at J2N.Numerics.ParseNumbers.StringToLong(String s, Int32 radix, Int32 flags, Int32 sign, Int32& currPos, Int32 length)

   at J2N.Numerics.Int64.Parse(String s, Int32 startIndex, Int32 length, Int32 radix)

   at Lucene.Net.Index.SegmentInfos.GetLastCommitGeneration(String[] files)

   at Lucene.Net.Index.SegmentInfos.FindSegmentsFile.Run(IndexCommit commit)

   at Lucene.Net.Index.SegmentInfos.Read(Directory directory)

   at Lucene.Net.Index.IndexWriter..ctor(Directory d, IndexWriterConfig conf)

   at RedGate.SqlPrompt.SqlHistory.Storage.Search.Indexing.IndexWriterWrapper..ctor(Directory directory)

   at RedGate.SqlPrompt.SqlHistory.Storage.Search.Indexing.Indexer.ReIndex(IDbCommand command)

   at RedGate.SqlPrompt.SqlHistory.Storage.Search.Indexing.Indexer.Index(IDbCommand command)

   at RedGate.SqlPrompt.SqlHistory.Storage.Search.CacheInitializer.Initialize(String sqlHistoryPath)

cperez

Good Afternoon @prozach99,

Thanks for reaching out to Redgate Support and sorry to hear you are having some trouble with SQL Search. I have seen this issue in the past sometimes be caused by the user having an out-of-date version of SQL Search installed. Could I kindly have you confirm you have SQLSearch_3.7.0.4929.exe installed in this environment, and if not, install it and confirm if you are still seeing this issue?