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

80
3
Jump to solution
10-03-2017 04:50 AM
Highlighted
Regular Contributor

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:

Reply
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Regular Contributor

Nevermind, all I had to do was change the Alias which somehow was set as the old database name...

View solution in original post

3 Replies
Highlighted
Regular Contributor

Nevermind, all I had to do was change the Alias which somehow was set as the old database name...

View solution in original post

Highlighted
Honored Contributor

When you copy-pasted the features from one schema/database to another, it changes the Full Table Name, but the Alias Name remains unchanged. When you add the Feature Class/ Table to ArcMap, the LayerName shows the alias name, not the table name. 

If you change the Alias Name in the Properties of the Feature Class in ArcCatalog, then the Layer Name will show as you desired.

Highlighted
Honored Contributor

You got it right before I could suggest.

Reply
0 Kudos