--- title: Non-Historized Satellite description: A Non-Historized Satellite stores the descriptive data of each Hub key once, without row hash and validity, in a table of the Raw Vault layer. --- [Skip to content](https://knowledge.bigenius-x.com/non-historized-satellite#main-content) [Contact us](https://knowledge.bigenius-x.com/kb-tickets/new?hsLang=en) [Go to Customer Portal](https://knowledge.bigenius-x.com/customer-portal?hsLang=en) [![TRI\_Logo\_biGENIUS\_2020\_RGB\_s](https://knowledge.bigenius-x.com/hs-fs/hubfs/Marketing/TRI_Logo_biGENIUS_2020_RGB_s.png?width=150&height=42&name=TRI_Logo_biGENIUS_2020_RGB_s.png)](https://www.bigenius-x.com/) Open main navigation Close main navigation - [Contact us](https://knowledge.bigenius-x.com/kb-tickets/new) - [Go to Customer Portal](https://knowledge.bigenius-x.com/customer-portal) How can we help you? - There are no suggestions because the search field is empty. 1. [biGENIUS-X Knowledge Base](https://knowledge.bigenius-x.com/?hsLang=en) 2. [Generators](https://knowledge.bigenius-x.com/generators?hsLang=en) 3. [Model Object Type](https://knowledge.bigenius-x.com/generators?hsLang=en#model-object-type) # Non-Historized Satellite **Applies to** Platform: Microsoft SQL Server · Snowflake · Snowflake dbt · Databricks · Databricks dbt · Fabric Lakehouse · Fabric Warehouse · Oracle Architecture: Data Vault A Non-Historized Satellite stores the descriptive data of each Hub key once, without row hash and validity, in a table of the Raw Vault layer. Use it for data that does not change after it arrives, such as the details of a sales transaction. After each load, the result view shows one row per loaded Hub key with the load that inserted it. A Non-Historized Satellite works like a [Non-Historized Link Satellite](https://knowledge.bigenius-x.com/non-historized-link-satellite?hsLang=en), but it belongs to a [Hub](https://knowledge.bigenius-x.com/hub?hsLang=en) instead of a Link. Available since Generator 2.4. ### Sources and relationships A Non-Historized Satellite reads [Stages](https://knowledge.bigenius-x.com/stage?hsLang=en) and [RawVault Composites](https://knowledge.bigenius-x.com/rawvault-composite?hsLang=en), and [Store Entities](https://knowledge.bigenius-x.com/store-entity?hsLang=en) of a linked Data Store project, in one or more dataflows. It has exactly one relationship to a Hub, and its foreign-key terms must be mapped. [BusinessVault Composite](https://knowledge.bigenius-x.com/businessvault-composite?hsLang=en), [Vault Out](https://knowledge.bigenius-x.com/vault-out?hsLang=en) and the Business Vault types can read it; Current View, History View and PIT do not accept it. ### Create the model object - With the wizard: open the menu of a Stage, RawVault Composite or Store Entity, choose **Automate** and then **Create Non-Historized Satellite**. Its steps are [Create Model Object](https://knowledge.bigenius-x.com/wizard-step-create-model-object?hsLang=en), [Create Dataflow](https://knowledge.bigenius-x.com/wizard-step-create-dataflow?hsLang=en), [Create Relations](https://knowledge.bigenius-x.com/wizard-step-create-relations?hsLang=en), [Map Foreign Key Terms](https://knowledge.bigenius-x.com/wizard-step-map-foreign-key-terms?hsLang=en), [Map Selected Terms](https://knowledge.bigenius-x.com/wizard-step-map-selected-terms?hsLang=en) and [Add to View](https://knowledge.bigenius-x.com/wizard-step-add-to-view?hsLang=en). See [Create a Model Object with the wizard](https://knowledge.bigenius-x.com/create-a-model-object-with-the-wizard?hsLang=en). - Manually: [create a model object](https://knowledge.bigenius-x.com/create-a-model-object?hsLang=en) of type Non-Historized Satellite in the Raw Vault layer, [add a relationship](https://knowledge.bigenius-x.com/add-a-relationship?hsLang=en) to the Hub, [create a dataflow set](https://knowledge.bigenius-x.com/create-a-data-flow-set?hsLang=en), [add the source model object](https://knowledge.bigenius-x.com/add-a-model-object-into-a-data-flow-set?hsLang=en) and [map the foreign-key terms and the descriptive terms](https://knowledge.bigenius-x.com/map-a-source-term-with-a-target-term?hsLang=en). ### Loading behavior The Non-Historized Satellite loads each Hub key once. Later rows for the same Hub key are not loaded, even when their values differ. The loader only inserts rows; it never updates or deletes them. With an incremental load, a row whose `BG_IncrementalFilter` is not above the stored increment is not read, in this or a later load. ### Properties - [Implementation Type](https://knowledge.bigenius-x.com/implementation-type-model-object?hsLang=en): `Permanent` only. - [Foreign Key Mode](https://knowledge.bigenius-x.com/foreign-key-mode-model-object?hsLang=en): whether the table gets a foreign key to the Hub table. With `Create Disabled`, the default, it is created and disabled. - [Load Caching](https://knowledge.bigenius-x.com/load-caching-model-object?hsLang=en): empty (default) or `Hashing`, which stores the hashing view in a table before the loader runs. - [Increment Management Type](https://knowledge.bigenius-x.com/increment-management-type-model-object?hsLang=en): `Auto` (default) or `User`, for an incremental load with [`BG_IncrementalFilter`](https://knowledge.bigenius-x.com/bg_incrementalfilter?hsLang=en). See [Configure an incremental load](https://knowledge.bigenius-x.com/configure-an-incremental-load?hsLang=en). - [Deduplication Method](https://knowledge.bigenius-x.com/deduplication-method-dataflow?hsLang=en) and [Sort Order within Partition](https://knowledge.bigenius-x.com/sort-order-within-partition-dataflow?hsLang=en), per dataflow. - [Use Embryo Loader](https://knowledge.bigenius-x.com/embryo-loader?hsLang=en), on the relationship: inserts Hub keys that the Hub does not hold yet. Persist Validity and Version Valid From Term do not apply. ### Default Terms - [`Hub_HK`](https://knowledge.bigenius-x.com/hub_hk?hsLang=en): the key of the Hub row, calculated from the foreign-key terms, and primary key of the table. - [`BG_LoadTimestamp`](https://knowledge.bigenius-x.com/bg_loadtimestamp?hsLang=en): the load that inserted the row. - [`BG_SourceSystem`](https://knowledge.bigenius-x.com/bg_sourcesystem?hsLang=en): the source system, empty unless you map it. - [`BG_IncrementalFilter`](https://knowledge.bigenius-x.com/bg_incrementalfilter?hsLang=en): source term for an incremental load; not stored in the table. - [`BG_DataQuality_ID`](https://knowledge.bigenius-x.com/bg-dataquality-id?hsLang=en), [`BG_ErrorCount`](https://knowledge.bigenius-x.com/bg_errorcount?hsLang=en) and [`BG_ErrorDescription`](https://knowledge.bigenius-x.com/bg_errordescription?hsLang=en): hidden terms of the data quality objects. There is no `BG_RowHash`, `BG_ValidFromTimestamp` or `BG_ValidToTimestamp`. ### Generated objects These are the names on Microsoft SQL Server for the Non-Historized Satellite `load_nsat` with one dataflow: | Role | Generated name | Purpose | | --- | --- | --- | | IncrementSource | `RDV_NHSAT_load_nsat_IncrementSource` | Finds the new increment | | Increment | `RDV_NHSAT_load_nsat_Increment` | Stores the increments | | Source | `RDV_NHSAT_load_nsat_Source` | Reads the sources | | Deduplication | `RDV_NHSAT_load_nsat_Deduplication` | Removes duplicate rows | | Hashing | `RDV_NHSAT_load_nsat_Hashing` | Calculates `Hub_HK` | | HashingStorage | `RDV_NHSAT_load_nsat_HashingTable` | Stores the hashed rows | | HashingLoader | `RDV_NHSAT_load_nsat_HashingLoader` | Fills the hashing table | | EmbryoLoader | `RDV_NHSAT_load_nsat_EmbryoLoader` | Adds missing Hub keys | | Delta | `RDV_NHSAT_load_nsat_Delta` | Selects new Hub keys | | Loader | `RDV_NHSAT_load_nsat_Loader` | Inserts the new rows | | Storage | `RDV_NHSAT_load_nsat` | Non-Historized Satellite table | | Result | `RDV_NHSAT_load_nsat_Result` | Query view | - Loaders are stored procedures; the satellite table, the increment table and the hashing table are tables; all other objects are views. - The increment table exists only with an incremental load, that is, when a dataflow maps `BG_IncrementalFilter`; the increment source view only with Increment Management Type `Auto`. - The deduplication view exists only with a Deduplication Method other than `None`. - The hashing table and hashing loader exist only with Load Caching `Hashing`. - The embryo loader exists only when Use Embryo Loader is true on the relationship. - With several dataflows, all objects except the table, the result view and the increment table exist once per dataflow, with the dataflow name in their names. The example object loads incrementally, so a load runs this chain: ``` _IncrementSource -> _Loader -> _Increment (new increment) sources + _Increment -> _Source -> _Hashing -> _Delta _Delta -> _Loader -> RDV_NHSAT_load_nsat -> _Result _Result -> _Delta (Hub keys already stored) ``` The loader first stores the new increment, the highest `BG_IncrementalFilter` of the source. The source view reads the rows between the previous and the new increment. The delta view keeps the rows whose `Hub_HK` is not in the result view, and the loader inserts them. Without an incremental load, the chain starts at `_Source`. ### Example The Non-Historized Satellite `load_nsat` on Microsoft SQL Server reads the Stage `SALESTRANSACTION`. It has a relationship to the Hub `common_salestransaction`, whose business keys are `TRANSACTION_ID` and `TRANSACTION_LINE_NO`. `BG_IncrementalFilter` is mapped to `TRANSACTION_TIME`, with Increment Management Type `Auto`. `QUANTITY` and `TRANSACTION_TIME` are mapped as descriptive terms. The loads deliver these transaction lines: - Load 1 on 2026-11-09 08:00: transaction 1001, line 1 with quantity 2 and line 2 with quantity 1, both with transaction time 2026-11-09 07:00. - Load 2 on 2026-11-10 08:00: 1001 line 1 again, now with quantity 3 and transaction time 2026-11-10 07:00. The new transaction 1002 arrives with line 1, quantity 4 and transaction time 2026-11-10 07:30. - Load 3 on 2026-11-11 08:00: the rows of load 2 again, and the new transaction 1003 with line 1, quantity 1 and transaction time 2026-11-09 06:00. ### Check the result Query the result view with the business keys of the Hub, here in the schema `rawvault`: ``` SELECT h.TRANSACTION_ID, h.TRANSACTION_LINE_NO AS LINE_NO, s.QUANTITY, s.TRANSACTION_TIME AS TX_TIME, s.BG_LoadTimestamp FROM rawvault.RDV_NHSAT_load_nsat_Result AS s JOIN rawvault.RDV_HUB_common_salestransaction_Result AS h ON h.Hub_HK = s.Hub_HK ORDER BY h.TRANSACTION_ID, h.TRANSACTION_LINE_NO; ``` This is the result after load 3: ``` TRANSACTION_ID LINE_NO QUANTITY TX_TIME BG_LoadTimestamp 1001 1 2.000 2026-11-09 07:00 2026-11-09 08:00 1001 2 1.000 2026-11-09 07:00 2026-11-09 08:00 1002 1 4.000 2026-11-10 07:30 2026-11-10 08:00 ``` - 1001 line 1 keeps quantity 2 from load 1. Its row from load 2 was read, but its Hub key was already stored. - 1002 line 1 is a new Hub key and was loaded in load 2. - Load 3 inserted no row. No transaction time of load 3 lies above the stored increment 2026-11-10 07:30, so the source view reads none of its rows. ### Platform differences - Snowflake: names are in capitals, and the loader is a stored procedure. The load control task `LC_RDV_NHSAT__TASK` calls it. The dataflow properties [Use Stream](https://knowledge.bigenius-x.com/use-stream-model-object?hsLang=en) and [Warehouse Placeholder Variable Name](https://knowledge.bigenius-x.com/warehouse-placeholder-variable-name-dataflow?hsLang=en) apply. - Databricks and Fabric Lakehouse: table and view names are in lowercase, and the loader is the notebook `RDV_NHSAT__Loader`. The properties [File Format](https://knowledge.bigenius-x.com/file-format-model-object?hsLang=en), [Optimization Method](https://knowledge.bigenius-x.com/optimization-method-model-object?hsLang=en), [Optimization Method Columns](https://knowledge.bigenius-x.com/optimization-method-columns-model-object?hsLang=en) and [Use Sequential Dataflow Execution](https://knowledge.bigenius-x.com/use-sequential-dataflow-execution-model-object?hsLang=en) apply. Fabric Lakehouse allows only Foreign Key Mode `None`. - Databricks dbt and Snowflake dbt: the satellite becomes the dbt models `rdv_nhsat__source` and `rdv_nhsat_`. The second model is the table and inserts only Hub keys that it does not hold yet. The model `rdv_nhsat__result` is generated when Create Result Views is true; the default on dbt is false. Load Caching, Increment Management Type and Use Embryo Loader are not available. - Fabric Warehouse: the same objects as on Microsoft SQL Server, deployed by notebooks. - Oracle: names are in capitals, and the loader is a PL/SQL package. [Partition Clause](https://knowledge.bigenius-x.com/partition-clause-and-table-storage-model-object?hsLang=en) adds its text to the `CREATE TABLE` statement. Table Compression, the tablespaces and the statistics properties also apply. - Foreign Key Mode `Create Enforced` exists only on Microsoft SQL Server and Oracle. ### Limitations - A Non-Historized Satellite has exactly one relationship to a Hub. Business keys raise a validation warning. - Corrections of an already loaded Hub key do not reach the table. A [Satellite](https://knowledge.bigenius-x.com/satellite?hsLang=en) stores changing data with its history. - On Microsoft SQL Server, a dataflow that delivers the same Hub key twice in one load makes the loader fail with a primary key violation. ### Related articles - Previous: [Hub](https://knowledge.bigenius-x.com/hub?hsLang=en) - Next: [Configure an incremental load](https://knowledge.bigenius-x.com/configure-an-incremental-load?hsLang=en) - Reference: [Hub\_HK](https://knowledge.bigenius-x.com/hub_hk?hsLang=en), [BG\_IncrementalFilter](https://knowledge.bigenius-x.com/bg_incrementalfilter?hsLang=en), [Foreign Key Mode (Model Object)](https://knowledge.bigenius-x.com/foreign-key-mode-model-object?hsLang=en), [Load Caching (Model Object)](https://knowledge.bigenius-x.com/load-caching-model-object?hsLang=en) - See also: [Satellite](https://knowledge.bigenius-x.com/satellite?hsLang=en), [Non-Historized Link Satellite](https://knowledge.bigenius-x.com/non-historized-link-satellite?hsLang=en), [Non-Historized Business Satellite](https://knowledge.bigenius-x.com/non-historized-business-satellite?hsLang=en), [Embryo Loader](https://knowledge.bigenius-x.com/embryo-loader?hsLang=en), [Create a Model Object with the wizard](https://knowledge.bigenius-x.com/create-a-model-object-with-the-wizard?hsLang=en) - [Getting started](https://knowledge.bigenius-x.com/getting-started?hsLang=en#main-content) - [Guidelines](https://knowledge.bigenius-x.com/getting-started?hsLang=en#guidelines) - [Start working](https://knowledge.bigenius-x.com/getting-started?hsLang=en#start-working) - [Account](https://knowledge.bigenius-x.com/getting-started?hsLang=en#account) - [General overview](https://knowledge.bigenius-x.com/general-overview?hsLang=en) - [Artificial Intelligence](https://knowledge.bigenius-x.com/artificial-intelligence?hsLang=en) - [Application Modules](https://knowledge.bigenius-x.com/application-modules?hsLang=en#main-content) - [Administration](https://knowledge.bigenius-x.com/application-modules?hsLang=en#administration) - [Solutions](https://knowledge.bigenius-x.com/application-modules?hsLang=en#solutions) - [Global Features](https://knowledge.bigenius-x.com/application-modules?hsLang=en#global-features) - [Projects](https://knowledge.bigenius-x.com/application-modules?hsLang=en#projects) - [Branches](https://knowledge.bigenius-x.com/application-modules?hsLang=en#branches) - [Data Connections](https://knowledge.bigenius-x.com/application-modules?hsLang=en#data-connections) - [Dataflow Modeling - Overview](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-overview) - [Dataflow Modeling - Wizard Steps](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-wizard-steps) - [Dataflow Modeling - Terms](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-terms) - [Dataflow Modeling - Term Mapping](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-term-mapping) - [Dataflow Modeling - Relationships](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-relationships) - [Dataflow Modeling - Data Quality](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-data-quality) - [Dataflow Modeling - Indexes](https://knowledge.bigenius-x.com/application-modules?hsLang=en#dataflow-modeling-indexes) - [Relationship Modeling](https://knowledge.bigenius-x.com/application-modules?hsLang=en#relationship-modeling) - [Generate Artifacts](https://knowledge.bigenius-x.com/application-modules?hsLang=en#generate-artifacts) - [Project Settings](https://knowledge.bigenius-x.com/application-modules?hsLang=en#project-settings) - [Data Marketplace](https://knowledge.bigenius-x.com/application-modules?hsLang=en#data-marketplace) - [Generators](https://knowledge.bigenius-x.com/generators?hsLang=en#main-content) - [Fabric Warehouse](https://knowledge.bigenius-x.com/generators?hsLang=en#fabric-warehouse) - [Fabric Lakehouse](https://knowledge.bigenius-x.com/generators?hsLang=en#fabric-lakehouse) - [Databricks](https://knowledge.bigenius-x.com/generators?hsLang=en#databricks) - [Snowflake](https://knowledge.bigenius-x.com/generators?hsLang=en#snowflake) - [Microsoft SQL Server](https://knowledge.bigenius-x.com/generators?hsLang=en#microsoft-sql-server) - [Oracle](https://knowledge.bigenius-x.com/generators?hsLang=en#oracle) - [Artifacts](https://knowledge.bigenius-x.com/generators?hsLang=en#artifacts) - [Replace Placeholders](https://knowledge.bigenius-x.com/generators?hsLang=en#replace-placeholders) - [Target solution environment](https://knowledge.bigenius-x.com/generators?hsLang=en#target-solution-environment) - [Deployment](https://knowledge.bigenius-x.com/generators?hsLang=en#deployment) - [Deployment with an Azuze DevOps pipeline](https://knowledge.bigenius-x.com/generators?hsLang=en#deployment-with-an-azuze-devops-pipeline) - [Delta Deployment](https://knowledge.bigenius-x.com/generators?hsLang=en#delta-deployment) - [Load control environment](https://knowledge.bigenius-x.com/generators?hsLang=en#load-control-environment) - [Load data with a native load control](https://knowledge.bigenius-x.com/generators?hsLang=en#load-data-with-a-native-load-control) - [Load data with Apache Airflow](https://knowledge.bigenius-x.com/generators?hsLang=en#load-data-with-apache-airflow) - [Model Object Type](https://knowledge.bigenius-x.com/generators?hsLang=en#model-object-type) - [Properties](https://knowledge.bigenius-x.com/generators?hsLang=en#properties) - [Default Terms](https://knowledge.bigenius-x.com/generators?hsLang=en#default-terms) - [Discovery application](https://knowledge.bigenius-x.com/discovery-application?hsLang=en#main-content) - [Discovery configurations](https://knowledge.bigenius-x.com/discovery-application?hsLang=en#discovery-configurations) - [Best practices](https://knowledge.bigenius-x.com/best-practices?hsLang=en#main-content) - [Modeling Approaches](https://knowledge.bigenius-x.com/best-practices?hsLang=en#modeling-approaches) - [Use Cases](https://knowledge.bigenius-x.com/best-practices?hsLang=en#use-cases) - [Business Rules](https://knowledge.bigenius-x.com/best-practices?hsLang=en#business-rules) - [Data Quality Rules](https://knowledge.bigenius-x.com/best-practices?hsLang=en#data-quality-rules) - [FAQs](https://knowledge.bigenius-x.com/faqs?hsLang=en) - [Product Release Notes](https://knowledge.bigenius-x.com/product-release-notes?hsLang=en#main-content) - [SaaS Application](https://knowledge.bigenius-x.com/product-release-notes?hsLang=en#saas-application) - [Discovery application](https://knowledge.bigenius-x.com/product-release-notes?hsLang=en#discovery-application) - [Generators](https://knowledge.bigenius-x.com/product-release-notes?hsLang=en#generators) - [Legal Documents](https://knowledge.bigenius-x.com/legal-documents?hsLang=en#main-content) - [Current legal docs](https://knowledge.bigenius-x.com/legal-documents?hsLang=en#current-legal-docs) - [Software Product and Limits](https://knowledge.bigenius-x.com/legal-documents?hsLang=en#software-product-and-limits) - [Contact us](https://knowledge.bigenius-x.com/kb-tickets/new?hsLang=en) - [Customer Portal](https://knowledge.bigenius-x.com/customer-portal) - [Sign in](https://knowledge.bigenius-x.com/_hcms/mem/login) [![biGENIUS logo](https://knowledge.bigenius-x.com/hubfs/TRI_Logo_biGENIUS_2020_RGB-1.svg "biGENIUS logo")](https://www.bigenius-x.com) All rights reserved © 2025, biGENIUS AG