AnsweredAssumed Answered

Copying feature classes between enterprise geodatabases...old geodatabase name showing up in TOC?

Question asked by MollyKFoley on Oct 3, 2017
Latest reply on Oct 3, 2017 by jayanta.poddar

I copied and pasted a feature class from one enterprise geodatabase to another. In the catalog window, the naming scheme shows up correctly for the new database, but when I add the layer to the map, the naming scheme changes to the old database. New database is called FocalAreasTest1, old database is called FocalAreas. It only appears to affect the feature classes I copied over and not the tables. Any idea why this might be happening and how to fix it? The source looks correct, it's just the name in the TOC.

 

New database in catalog window naming scheme (FocalAreasTest1):

 

Added MonitoringPoint feature class to the TOC, along with a table that I also copied from old database to new using the same procedures as the feature classes, notice how they are both children of a single parent database (the new one):

 

Source window for the newly added MonitoringPoint feature class where it looks to come from the correct source:

Outcomes