I have an existing table called
Realms. This has the superkey
rlmID (just a surrogate key). We are planning to add tables that group realms in some context -- let's just calll them
RealmGroups. This will require adding a
realmGroupID column to
Realms. No problemo.
Realms will be part of
Realms.realmGroupID would be nullable. In this case, is it better to have a separate table (
RealmsRealmGroups) that has (
realmGroupID)? Since the superkey of
RealmsRealmGroups would be the same, I see no advantage to creating a separate table, but my DBA is suggesting that we should use a separate one for organizational purposes.
Are there any technical or practical reasons to use a separate table to store information for the same superkey?