Database Reference
In-Depth Information
Now that we have our entity relationship diagram, the consultant is ready to start working.
She first made a note of how attributes are duplicated between all the feature classes. In
case we need to add a new attribute or delete an existing one, we should make sure that
this change is reflected across all the geodatabase datasets to maintain data integrity. She
also mentioned that querying would be more difficult with this model as you have to hit
many tables to search for a record. Finally, the consultant pointed out that we have so
many tables in our design because of unnecessary relationships. In the upcoming sections,
we will learn how to remodel this design for more efficiency and less maintenance.
