# Making Satellite or Hub out of two tables **URL:** \ **Category:** Data Vault 2.0\ **Tags:** hub, satellite, vaultspeed\ **Created:** [May 8, 2023, 9:34am UTC](https://forum.data-community.org/t/making-satellite-or-hub-out-of-two-tables/777 "2023-05-08T09:34:12Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Faris](https://avatars.discourse-cdn.com/v4/letter/f/ee7513/32.png) [@Faris](https://forum.data-community.org/u/Faris)\ **Post date:** [May 8, 2023, 9:34am UTC](https://forum.data-community.org/t/making-satellite-or-hub-out-of-two-tables/777/1 "2023-05-08T09:34:12Z")
In source, I have two tables named Vendor\_Address, which has the primary key Address\_Id and other descriptive attributes like house\_number, street, etc. And nother table in the source named Vendor\_Email\_Address which has the same primary key Address\_Id and just one more attribute, Email\_address. If I have to build the source data vault out of these two tables, my approach would be to create Vendor\_Address as the hub, in which address\_id would be the business key and attach Vendor\_Email\_Address as another satellite for Vendor\_Address. Considering that for one business key, there would be only one hub. Please suggest if this is right or wrong? ---
**Author:** ![Nicruzer](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/nicruzer/32/38_2.png) [@Nicruzer](https://forum.data-community.org/u/Nicruzer)\ **Post date:** [May 8, 2023, 10:29pm UTC](https://forum.data-community.org/t/making-satellite-or-hub-out-of-two-tables/777/2 "2023-05-08T22:29:15Z")
@Faris - the answer is as Dan Linstedt himself likes to say, “It depends.” Things to consider to help you decide a good approach would be: - What is the business use case? - Have you captured the primary business concepts adequately? - Does each vendor have more than one email address active at once? (Hint: If so, a separate multi-active satellite makes sense for the email addresses, in my opinion.) - Is **Address\_Id** a true business key? (How does the business refer to any given unique vendor?) - Is **Vendor\_Address** truly a business concept, or is it a relationship? (Hint: Can a vendor’s address change over time? Can a vendor have more than one address? Does _address_ truly describe a vendor?) If I am interpreting your description, you plan to build a **Vendor\_Address** hub with two satellites, one of which captures the address information (low volatility) and the other which captures email address (possibly medium volatility or multi-active). Given my questions above (meant to trigger some thought), do you believe you have a good design? ---
**Author:** ![RhysHanscombe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/rhyshanscombe/32/394_2.png) [@RhysHanscombe](https://forum.data-community.org/u/RhysHanscombe)\ **Post date:** [December 1, 2025, 2:51pm UTC](https://forum.data-community.org/t/making-satellite-or-hub-out-of-two-tables/777/3 "2025-12-01T14:51:32Z")
Closed on December 1, 2025, 2:51pm UTC