It's in a design for a Membership Type system that keeps up with members, dues, attendance, progress, payment and attendance history, etc... Virtually every table in the database has...

Yes - the ooak (one-of-a-kind) number is a guid - - - I contend it is very wasteful and suggested an dumb number integer instead of the expensive 16-character guid...

I am not debating the Primary Key issue - it's the use of an "ooak" in every (over naturalized database) table and using the ooak's as 'the' relationship to children...