How to model IP Dimension
3 posters
Page 1 of 1
How to model IP Dimension
Hi,
We have a data warehousing system which is dedicated to the network attacks analysis.
The crucial dimensional information is a Source(Attackers) IPs and Destination (Target) IPs.
My question is: how would you recomend to model the Source and Destination IP dimensions.
Note:
The number of unique values in both of them can potentially grow up to billions of records.
Both IPv4 and IPv6 should be supported (IPv6 is stored as 2 bigint columns in fact table).
Thanks in advance,
Andriy
We have a data warehousing system which is dedicated to the network attacks analysis.
The crucial dimensional information is a Source(Attackers) IPs and Destination (Target) IPs.
My question is: how would you recomend to model the Source and Destination IP dimensions.
Note:
The number of unique values in both of them can potentially grow up to billions of records.
Both IPv4 and IPv6 should be supported (IPv6 is stored as 2 bigint columns in fact table).
Thanks in advance,
Andriy
andriy.zabavskyy- Posts : 18
Join date : 2011-09-12
Re: How to model IP Dimension
I'd go with degenerate dimension(s).
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: How to model IP Dimension
Did you recommend a degenerate dimension due to the large number of records?
cjrinpdx- Posts : 51
Join date : 2011-07-14
Location : Portland, OR
Re: How to model IP Dimension
I recommended since they are unique.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: How to model IP Dimension
Got ya, and maybe the lack of additional attributes would be a good reason to go with the degenerate dimension. If this dimension was going to be used with multiple fact tables that might be an argument to use a separate dimension table and create a conformed dimension.
cjrinpdx- Posts : 51
Join date : 2011-07-14
Location : Portland, OR
Re: How to model IP Dimension
Yes, but there are often times that there are additional attributes that need to be modeled into separate tables to reduce the cardinality down from a 1-1. Invoice # or Order # are common examples. There are plenty of Order and Invoice attributes that I could put into an Order or invoice dimension, but you will build a better performing model if you break those columns into smaller separate dimensions and store the order#/invoice# on the fact table. In this case, IP looks like it is a single column that is unique, so a DD looks like an optimal fit.
BoxesAndLines- Posts : 1212
Join date : 2009-02-03
Location : USA
Re: How to model IP Dimension
Please take into account that IP attribute is based on 2 bigint columns(mainly needed for IPv6). There could be added a string column for more friendly representation but I am not sure it is a good idea to create a DD based on it
andriy.zabavskyy- Posts : 18
Join date : 2011-09-12
Similar topics
» How do you model a dimension that behaves both as a dimension and a fact??
» ICD-9 to ICD-10 Dimension Model
» How can Model Employee Dimension?
» dimension model design:
» parent child dimension model
» ICD-9 to ICD-10 Dimension Model
» How can Model Employee Dimension?
» dimension model design:
» parent child dimension model
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|