Non spatial table created in SQL to be updated automatically daily. Table will be involved in a join so it is registered with the geodatabase in ArcCatalog, creating an OID in field called ObjectID. When the program is run in SQL to delete the table and recreate it using the same name, 0 records appear in ArcGIS. But it appears to be populated in SQL.
So my question is: If a table is registered with the geodatabase and then deleted in SQL and a new table is created with the same name (essentially overwriting the existing table), does the new one need to be re-registered with the geodatabase? Why else would the table appear to be empty when viewing in ArcMap?
Megan,
The reason why the data is being shown on sql but not on geodatabase is: The geodatabase honors objectid as a unique, not null integer field to uniquely identify rows in tables. However, SQL does not, even though a field very identical to OBJECTID is created.
Below is the caution provided by esri.
Caution:
Since most ArcGIS for Desktop functionality requires that the ObjectID be unique, you must be sure that ObjectID values are not duplicated when working directly with the database outside of ArcGIS. For example, when creating views with a one-to-many relationship, there is the possibility that ObjectIDs will be duplicated. This causes inconsistent behavior in ArcGIS for Desktop functionality.
One way to fix the issue is: by creating a GlobalID and treating it as a unique, not null integer.