How can we help you today? How can we help you today?
delapohl

Activity overview

Latest activity by delapohl

It looks like the log snippet got truncated in my post. Trying again: 13 Apr 2020 17:24:18.299 [74] ERROR DatabaseObjectIndexer - Exception while indexing database XXXXXXX_DEV: code = NotADb (26), message = System.Data.SQLite.SQLiteException (0x800007FF): file is not a database file is not a database    at System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)    at System.Data.SQLite.SQLiteCommand.BuildNextCommand()    at System.Data.SQLite.SQLiteCommand.GetStatement(Int32 index)    at System.Data.SQLite.SQLiteDataReader.NextResult()    at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)    at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)    at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior)    at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()    at System.Data.SQLite.SQLiteConnection.Open()    at RedGate.SQLSearch.Indexing.SQLite.SqliteDatabaseConnection.EnsureConnectionOpen()    at RedGate.SQLSearch.Indexing.SQLite.SqliteDatabaseConnection.CreateCommand()    at RedGate.SQLSearch.Indexing.SQLite.DatabaseObjectStorage.Initialise()    at RedGate.SQLSearch.Indexing.DatabaseObjectIndexer.Index(CancellationToken ) / comments
It looks like the log snippet got truncated in my post. Trying again:13 Apr 2020 17:24:18.299 [74] ERROR DatabaseObjectIndexer - Exception while indexing database XXXXXXX_DEV: code = NotADb (26), m...
0 votes
SQL Search not returning results for one database only
After upgrading SSMS to 18.5 and then upgrading SQL Search to 3.5.0.2590, SQL Search is failing to return results for one of my databases. From what I can tell, searches on any other database on th...
1 follower 2 comments 0 votes
Thanks Rob, that pointed me in the right direction. I had manual mappings for these tables from a previous release. I restored the default mappings for those tables, and that resolved the issue. / comments
Thanks Rob, that pointed me in the right direction. I had manual mappings for these tables from a previous release. I restored the default mappings for those tables, and that resolved the issue.
0 votes