How can we help you today? How can we help you today?
prozach99

Activity overview

Latest activity by prozach99

Sure thing, thank you for looking into it.  I've had it happen before but then it resolved itself, I'm not sure what caused it or fixed it. It would be nice to have a fix. / comments
Sure thing, thank you for looking into it.  I've had it happen before but then it resolved itself, I'm not sure what caused it or fixed it. It would be nice to have a fix.
0 votes
That version did not fix the issue. I'm attaching the log file from today that includes that error here. / comments
That version did not fix the issue. I'm attaching the log file from today that includes that error here.
0 votes
SQL History Search Not working
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 t...
2 followers 9 comments 0 votes
My current workaround is to use DB Browser for SQLite and run the query there. select * from QueryVersions where Contents like '%mentor%' Gets me what I need but not as easy as the integrated tool. / comments
My current workaround is to use DB Browser for SQLite and run the query there.select *from QueryVersionswhere Contents like '%mentor%'Gets me what I need but not as easy as the integrated tool.
0 votes
I see this at the beginning of the log for today. Is there a way to repair/clean the database? 2024-04-17 07:31:52.961 -04:00 [Information] Trimming history... 2024-04-17 07:31:53.115 -04:00 [Information] History trimming complete (time taken = 00:00:00.1536573) 2024-04-17 07:31:56.531 -04:00 [Information] [Startup status] Size on disk (bytes) = 75513856, Number of queries = 4212, Number of revisions = 9698, Highest revisions per query = 209, Longest contents (characters) = 907601 2024-04-17 07:31:56.558 -04:00 [Information] Indexing SQL History to C:\Users\zgelnett\OneDrive\Documents\WorkStuff\Settings\SSMS\SQL Prompt\SqlHistoryIndex... 2024-04-17 07:31:57.105 -04: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) / comments
I see this at the beginning of the log for today. Is there a way to repair/clean the database?2024-04-17 07:31:52.961 -04:00 [Information] Trimming history...2024-04-17 07:31:53.115 -04:00 [Informa...
0 votes
I found this in the sql history error log: 2024-04-17 13:56:24.674 -04:00 [Error] Error processing command: StoreContentsRevision 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.IndexUpdater.GetCurrentState(Guid queryIdentity)    at RedGate.SqlPrompt.SqlHistory.Storage.Search.Indexing.IndexUpdater.AddContentsRevision(Guid queryIdentity, String name, String path, String contents, SqlHistoryConnection connection, DateTime dateSaved, Guid queryVersionIdentity, String originalName, String originalPath, String originalContents, SqlHistoryConnection originalConnection, DateTime originalDateSaved)    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.Handle(CommandOperation operation) 2024-04-17 14:01:29.903 -04:00 [Error] Error while searching for 'bank' (page: 1, object type: Everything, start date: <not set>, end date: <not set>, server: <not set>, database: <not set>, starred state: NotSet, open state: NotSet, sort: Relevance): Additional non-parsable characters are at the end of the string. / comments
I found this in the sql history error log:2024-04-17 13:56:24.674 -04:00 [Error] Error processing command: StoreContentsRevisionSystem.FormatException: Additional non-parsable characters are at the...
0 votes