# Enddate and IsCurrent Columns

**URL:** <https://forum.data-community.org/t/enddate-and-iscurrent-columns/338>\
**Category:** Data Vault 2.0\
**Created:** [June 21, 2022, 2:43pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338 "2022-06-21T14:43:27Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bigguy365](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/bigguy365/32/129_2.png) [@Bigguy365](https://forum.data-community.org/u/Bigguy365)\
**Post date:** [June 21, 2022, 2:43pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/1 "2022-06-21T14:43:27Z")

</div>

Having recently attended the CDV2P training and attaining the CDV2P-Legacy certification, PerfpormanceG2 is providing free of charge the DV101-Baseline Hands-On training course. The material was created in January of 2022 and is supposed to represent the current guidelines of the methodology. It has raised a question for me when Dan talked about different types of satellite tables as shown below.

SELECT orgcd\_country\_lhk,  
ldts,  
rsrc,  
org\_code\_hk\_dk,  
start\_date,  
end\_date,  
iscurrent,  
old\_orgcd\_country\_lhk,  
old\_ldts  
FROM **baseline\_vault.bv\_organization\_country\_effsat** ;

and

SELECT org\_sameas\_lhk,  
ldts,  
rsrc,  
org\_sameas\_hdiff,  
from\_org\_code\_hk\_dk,  
start\_date,  
end\_date,  
iscurrent,  
old\_org\_sameas\_lhk,  
old\_ldts  
FROM **baseline\_vault.rv\_orgcode\_hist\_sal\_effsat;**

I was under the impression that updates were deprecated in 2.0. In the above table, he has a start date column as expected. However, there are also the end date and iscurrent columns that require an update to correctly represent the data. Furthermore, there was nothing in the course about keeping previous primary key values that allowed for creating a reverse link list – although I do like the idea. Getting back to my topic, is having the end data and iscurrent columns a best practice?  
Thanks  
Clay

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [June 21, 2022, 4:44pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/2 "2022-06-21T16:44:50Z")

</div>

They are deprecated 😀

The source might be a dim or an MDM model that uses start and end dates too!

Look up IBM’s MDM (public domain) and you’ll see things like location\_group that maps parties to addresses and manages its own effectivity that we simply capture and load into the DV as INSERT-ONLY.

IBM MDM model is an example of an enterprise data model that is designed to serve as many industry models as possible, the thought, is that you’ll end up with a lot more tables to ingest!

---

<div class="post-metadata">

**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:** [June 21, 2022, 6:56pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/3 "2022-06-21T18:56:42Z")

</div>

@Bigguy365 - Did you watch the associated videos in the DV101-Baseline Hands-On training course? I watched them over a month ago, and I believe (if I remember correctly) that he explains why those fields are included in these satellites.

If I still have access to them, I will review them and let you know what I find (unless you find it first).

---

<div class="post-metadata">

**Author:** ![Bigguy365](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/bigguy365/32/129_2.png) [@Bigguy365](https://forum.data-community.org/u/Bigguy365)\
**Post date:** [June 21, 2022, 7:39pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/4 "2022-06-21T19:39:40Z")

</div>

@Nicruzer - Yes I watched all 32 videos and yes he does explain why he used them. His explanation is contrary to what was taught in the class and that was INSERT ONLY. That’s why I posted the question for clarification. According to Patrick – they are deprecated.

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [June 22, 2022, 1:53pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/5 "2022-06-22T13:53:50Z")

</div>

Yup

> **[DVModelingSpecs2-0-1.pdf](https://danlinstedt.com/wp-content/uploads/2018/06/DVModelingSpecs2-0-1.pdf)**

I believe a new standard will be released soon

---

<div class="post-metadata">

**Author:** ![bmccartney](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/bmccartney/32/43_2.png) [@bmccartney](https://forum.data-community.org/u/bmccartney)\
**Post date:** [June 24, 2022, 8:21am UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/6 "2022-06-24T08:21:32Z")

</div>

Hi All,  
In the videos created by DVA, Dan explains that the _effectivity satellite_ is a ‘derived’ object and thus considered BVish and thus not subject to the insert only restriction. I think he also provides and example of a effectivity satellite pattern that does not require updates but doesn’t have the active flag/end date.

So, raw DV update only, not end\_dates. BV is less restrictive, same principles apply but not standardized.

Hope that helps.

Bruce

---

<div class="post-metadata">

**Author:** ![Bigguy365](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/bigguy365/32/129_2.png) [@Bigguy365](https://forum.data-community.org/u/Bigguy365)\
**Post date:** [June 24, 2022, 12:05pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/7 "2022-06-24T12:05:33Z")

</div>

Hey Bruce. Thanks for the clarification. Regards Clay

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [June 24, 2022, 2:49pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/8 "2022-06-24T14:49:18Z")

</div>

Hey Bruce

Effectivity satellites are insert only  
They have end dates, physicalised

In my book I show how to build them and query them

They definitely don’t grey the line of DV2.0 INSERT ONLY principles

Complex and why I recommend that relationship effectivity solved at the source before implementing EFS

It’s is a Raw Vault artefact when source cannot resolve flip flopping relationships for you  
It’s business Vault if you are defining a driver key different to how the source defines it. Yes it can be both!

NO UPDATE! Only INSERT

😀

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [June 24, 2022, 3:28pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/9 "2022-06-24T15:28:50Z")

</div>

Example: [Data Vault Mysteries… Effectivity Satellite & Driving Key | by Patrick Cuba | Snowflake | Medium](https://medium.com/snowflake/data-vault-mysteries-effectivity-satellite-driving-key-5e96b5aab821)

---

<div class="post-metadata">

**Author:** ![Nat](https://avatars.discourse-cdn.com/v4/letter/n/8c91f0/32.png) [@Nat](https://forum.data-community.org/u/Nat)\
**Post date:** [April 27, 2023, 1:15pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/10 "2023-04-27T13:15:28Z")

</div>

It might be that the effsats you are showing there are actually views. If you look at what scalefree did in their dbt4datavault package (which forked from the sponsors of this eminent forum’s version dbtvault) they have a sat \_v0 which is an insert only table, and then a sat which has the is\_current and the end date as calculated fields in the view.

---

<div class="post-metadata">

**Author:** ![jmamedov](https://avatars.discourse-cdn.com/v4/letter/j/e274bd/32.png) [@jmamedov](https://forum.data-community.org/u/jmamedov)\
**Post date:** [July 11, 2023, 8:24am UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/11 "2023-07-11T08:24:59Z")

</div>

Hey Patrick.  
I have read your book but, it does not answer how you can have insert only end dates in effectivity satellite. It talks about how to generate virtual end date. All the related examples (pictures) have an explicit end date defined. Maybe you can point a specific page. The bottom line is if you have column end date (not virtual but a part of the schema ) then you would need to close it somehow.  
Thanks.

---

<div class="post-metadata">

**Author:** ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)\
**Post date:** [July 11, 2023, 8:51am UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/12 "2023-07-11T08:51:15Z")

</div>

That is incorrect — I reckon you need to go back to the book

I wrote about

- Where to model it
- How to load it
- How to query it

---

<div class="post-metadata">

**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:38pm UTC](https://forum.data-community.org/t/enddate-and-iscurrent-columns/338/13 "2025-12-01T14:38:33Z")

</div>


