Feature dataset view in sql broke

becyr

Has anyone into this issue of the feature dataset view breaking and seeing the evw. If yes, what is the solution?

Thanks,

George_Thompson

This screenshot looks like what I would see with a non-geodatabase on SQL Server.

How was the connect made? Can you provide a screenshot, block out the sensitive information?

When was the last time that connection looked "correct"?

--- George T.

becyr

Hi George,

This issue is what I am seeing both on an operating system and database authentication.

Everything was looking good until yesterday. IT help setup a nightly import in the sql server using a dbo user. Which I am 90% sure that it triggered the issue.

@George_Thompson

George_Thompson

Yeah, it looks like the geodatabase part of the database is broken.

Any idea what the "nightly import" is that they did?

Is the Enterprise Geodatabase a DBO or SDE schema?

It may be best to work with technical support on this.

The other option is restoring the last verified backup and work from there. You may potentially loose some work.

--- George T.

becyr

It's a table view from a tyler system. I am not sure if it was in a csv or xls.

The user updating the data is not the sde or dbo user, the table was owned by a dbo user.

The SQL Server is a SDE schema Restoring the last backup is something we are looking at, but it would be nice to resolve this issue and still have the nightly import.

George_Thompson

Thanks for that information. I am just not sure how an import from a file would "break" the EGDB.

How are they importing the data: ArcPy / Pro, straight SQL, other method?

I think that something in their import process impacted the repository (SDE) tables and caused this issue. It is hard to troubleshoot this without looking at all the pieces.

--- George T.

becyr

They are importing straight in SQL. No contact with the ArcGIS Environment. I did submit a Esri Ticket, the analyst did say it would take a bit of researching on their end to see what the issue might be.

George_Thompson

They may not have contact with the ArcGIS software, but there is "ArcGIS" things in the SQL database that may have been impacted.

Did they modify / update / touch any of the "SDE_" repository tables in the process?

--- George T.

becyr

Not certain, it for sure had to do with the import. We did decide to restore to the last verified backup. Should we stop any ArcGIS Server Services? What will be the best resource.

George_Thompson

I would recommend stopping all services that are touching the SQL EGDB before doing a restore. Make sure you sync all the logins to the SQL Instance AFTER the restore: https://support.esri.com/en-us/knowledge-base/re-synch-sql-server-logins-or-users-after-restoring-a-...

Once the restore is completed, re-synced, and verified, you should be able to allow connections and start the services.

--- George T.