Scribd
Upload
23 views4 pages

25.1 Multiactive Satellite

The document discusses different ways to implement multi-active satellites in a Data Vault 2.0 model. A multi-active satellite allows you to store multiple active records for a business key at a time. It provides examples of when to use a multi-active satellite, such as when receiving customer data with multiple phone numbers in an XML file. The document outlines three approaches to implementing multi-active satellites: using sub-sequence numbers, defining record types, or adding an extra hub.

Uploaded by

Diego Fernando Galicia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views4 pages

25.1 Multiactive Satellite

The document discusses different ways to implement multi-active satellites in a Data Vault 2.0 model. A multi-active satellite allows you to store multiple active records for a business key at a time. It provides examples of when to use a multi-active satellite, such as when receiving customer data with multiple phone numbers in an XML file. The document outlines three approaches to implementing multi-active satellites: using sub-sequence numbers, defining record types, or adding an extra hub.

Uploaded by

Diego Fernando Galicia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

USING MULTI-ACTIVE

SATELLITES
THE CORRECT WAY.

A multi-active satellite is similar to a standard satellite and its structure.


Using multi-active satellites, you’re able to store multiple active records
for one business key, at a point in time. See the exemple Data Vault model
in figure 1.

Figure 1: Data Vault model


Depending on how the data arrives from your source, there are different
ways to implement multi-activity (also referred as ‘multi-variant’ or ‘multi-
valued’) behavior Satellite, in Data Vault 2.0.

An example of when to use a Multi-active Satellite.

We refer to multi-active when you want to associate context (Satellite)


to a specific business concept (Hub) but it just doesn’t quite fit the granularity.
Or to be more precise: A Satellite that houses multiple active records (valid
values) for a given business key for a specific point in time.

Let’s say you get your customer’s data delivered in semi-structured XML-
files. Within it are several phone numbers in an array. But the metadata
doesn’t provide more information. So, the number, type, and order of the
records are unknown. When flattening the XML-file, you will receive as many
records as the number of tuples in the array as follows:
If you create a standard satellite out of these, only one row per customer
business key can be active at the same time. Otherwise, you would run into
a primary key violation having the same hash key and LDTS.

To avoid these problems, and also be able to query the active phone numbers
at any point in time, a “multi-active key” can be used. In case you don’t have a
multi-active key, you need to create your own one by adding a sub-sequence
number (per business key) into your current (Hash Key & LDTS) primary
Key.

Here, though, you have to pay close attention if the data changes in the next
load, For example, if the order of the phone numbers change , you cannot
assign a specific phone number to a sub-sequence (because this change of
order has made that pre-established sequence, will not be valid any more)

TYPES.

In case it is possible to define the type of codes and add them to the source
feed, the best approach is to add these, to the primary key of the Satellite.
Here, you rarely need to change types as well. In our example, we would
define types like ‘home’, ‘business’, ‘cell’ and ‘fax’ as shown in the next
figure. But remember, this must delivered by the source system. If not, you
have to use the sub-sequences.

ADDING AN EXTRA HUB.

The last way to solve issues regarding multi-active records is to create an


extra, weaker hub for the multi-active attribute, in this case the phone number,
and link them to the main hub. This requires that this attribute qualifies as a
business key. Here, the number of hubs may increase heavily depending on
how many multi-active data sets per business key you have. Furthermore, the
new hub might not present as a real business object. So, while this is not the
first way to go, it is a feasible solution in some cases.

You might also like