A database from a SQL discovery could not be saved to the ER database because the owner could not be properly identified.
An error message similar to the one below might appears in the ER log files:
<le ts="2025-03-14T19:26:37.3146786Z" l="ERROR" s="Quest.Data.LDM.LogicalDataModel.EntityManager" t="7f0c81ed-2c6f-44a1-b10c-e9cd1b568007"><m>Error saving data entity: SSISDB</m><ex>Quest.Data.LDM.LogicalDataModel.Exceptions.LDMException: Unable to save entity into database: INSERT INTO [dbo].[tblSQLServerDatabase] ([SQLServerDatabaseID], [LDM_TOMBSTONED], [OwnerAccountID], [DatabaseName], [LDM_TIMESTAMP], [SQLServerID]) VALUES (@P0, @P1, @P2, @P3, @P4, @P5) - SSISDB
@P0 - 8931224714511983270@P1 - False@P2 - 0@P3 - SSISDB@P4 - 3/14/2025 7:26:37 PM@P5 - -523076564883181059 ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_tblSQLServerDatabase_OwnerAccountID_tblAccount". The conflict occurred in database "dbReporter", table "dbo.tblAccount", column 'AccountID'.
The statement has been terminated.
The database that is failing to be saved might not have assigned an owner within the database's properties.
Assign an owner to the affected database and execute the SQL discovery again.
