As organizations consolidate analytics workloads to Databricks, they typically must adapt conventional knowledge warehouse methods. This collection explores the best way to implement dimensional modeling—particularly, star schemas—on Databricks. The primary weblog targeted on schema design. This weblog walks by way of ETL pipelines for dimension tables, together with Slowly Altering Dimensions (SCD) Sort-1 and Sort-2 patterns. The final weblog will present you the best way to construct ETL pipelines for truth tables.
Slowly Altering Dimensions (SCD)
Within the final weblog, we outlined our star schema, together with a truth desk and its associated dimensions. We highlighted one dimension desk specifically, DimCustomer, as proven right here (with some attributes eliminated to preserve area):
The final three fields on this desk, i.e., StartDate, EndDate and IsLateArriving, characterize metadata that assists us with versioning information. As a given buyer’s revenue, marital standing, house possession, variety of youngsters at house, or different traits change, we’ll need to create new information for that buyer in order that details similar to our on-line gross sales transactions in FactInternetSales are related to the suitable illustration of that buyer. The pure (aka enterprise) key, CustomerAlternateKey, would be the identical throughout these information however the metadata will differ, permitting us to know the interval for which that model of the shopper was legitimate, as will the surrogate key, CustomerKey, permitting our details to hyperlink to the suitable model.
NOTE: As a result of the surrogate secret’s generally used to hyperlink details and dimensions, dimension tables are sometimes clustered primarily based on this key. In contrast to conventional relational databases that make the most of b-tree indexes on sorted information, Databricks implements a singular clustering methodology often known as liquid clustering. Whereas the specifics of liquid clustering are exterior the scope of this weblog, we constantly use the CLUSTER BY clause on the surrogate key of our dimension tables throughout their definition to leverage this function successfully.
This sample of versioning dimension information as attributes change is named the Sort-2 Slowly Altering Dimension (or just Sort-2 SCD) sample. The Sort-2 SCD sample is most well-liked for recording dimension knowledge within the basic dimensional methodology. Nevertheless, there are different methods to cope with modifications in dimension information.
Some of the widespread methods to cope with altering dimension values is to replace present information in place. Just one model of the report is ever created, in order that the enterprise key stays the distinctive identifier for the report. For numerous causes, not the least of that are efficiency and consistency, we nonetheless implement a surrogate key and hyperlink our truth information to those dimensions on these keys. Nonetheless, the StartDate and EndDate metadata fields that describe the time intervals over which a given dimension report is taken into account energetic aren’t wanted. This is named the Sort-1 SCD sample. The Promotion dimension in our star schema offers a great instance of a Sort-1 dimension desk implementation:
However what concerning the IsLateArriving metadata subject seen within the Sort-2 Buyer dimension however lacking from the Sort-1 Promotion dimension? This subject is used to flag information as late arriving. A late arriving report is one for which the enterprise key exhibits up throughout a truth ETL cycle, however there isn’t a report for that key positioned throughout prior dimension processing. Within the case of the Sort-2 SCDs, this subject is used to indicate that when the info for a late arriving report is first noticed in a dimension ETL cycle, the report ought to be up to date in place (identical to in a Sort-1 SCD sample) after which versioned from that time ahead. Within the case of the Sort-1 SCDs, this subject isn’t mandatory as a result of the report might be up to date in place regardless.
NOTE: The Kimball Group acknowledges extra SCD patterns, most of that are variations and combos of the Sort-1 and Sort-2 patterns. As a result of the Sort-1 and Sort-2 SCDs are probably the most regularly applied of those patterns and the methods used with the others are carefully associated to what’s employed with these, we’re limiting this weblog to simply these two dimension sorts. For extra details about the eight forms of SCDs acknowledged by the Kimball Group, please see the Slowly Altering Dimension Methods part of this doc.
Implementing the Sort-1 SCD Sample
With knowledge being up to date in place, the Sort-1 SCD workflow sample is probably the most easy of the two-dimensional ETL patterns. To help a majority of these dimensions, we merely:
- Extract the required knowledge from our operational system(s)
- Carry out any required knowledge cleaning operations
- Evaluate our incoming information to these already within the dimension desk
- Replace any present information the place incoming attributes differ from what’s already recorded
- Insert any incoming information that don’t have a corresponding report within the dimension desk
As an example a Sort-1 SCD implementation, we’ll outline the ETL for the continued inhabitants of the DimPromotion desk.
Step 1: Extract knowledge from an operational system
Our first step is to extract the info from our operational system. As our knowledge warehouse is patterned after the AdventureWorksDW pattern database supplied by Microsoft, we’re utilizing the carefully related AdventureWorks (OLTP) pattern database as our supply. This database has been deployed to an Azure SQL Database occasion and made accessible inside our Databricks surroundings by way of a federated question. Extraction is then facilitated with a easy question (with some fields redacted to preserve area), with the question outcomes persevered in a desk in our staging schema (that’s made accessible solely to the info engineers in our surroundings by way of permission settings not proven right here). That is however one among some ways we are able to entry supply system knowledge on this surroundings:
Step 2: Evaluate incoming information to these within the desk
Assuming we have now no extra knowledge cleaning steps to carry out (which we might implement with an UPDATE or one other CREATE TABLE AS assertion), we are able to then sort out our dimension knowledge replace/insert operations in a single step utilizing a MERGE assertion, matching our staged knowledge and dimension knowledge on the enterprise key:
One essential factor to notice concerning the assertion, because it’s been written right here, is that we replace any present information when a match is discovered between the staged and printed dimension desk knowledge. We might add extra standards to the WHEN MATCHED clause to restrict updates to these situations when a report in staging has completely different info from what’s discovered within the dimension desk, however given the comparatively small variety of information on this explicit desk, we’ve elected to make use of the comparatively leaner logic proven right here. (We are going to use the extra WHEN MATCHED logic with DimCustomer, which accommodates way more knowledge.)
The Sort-2 SCD sample
The Sort-2 SCD sample is a little more advanced. To help a majority of these dimensions, we should:
- Extract the required knowledge from our operational system(s)
- Carry out any required knowledge cleaning operations
- Replace any late-arriving member information within the goal desk
- Expire any present information within the goal desk for which new variations are present in staging
- Insert any new (or new variations) of information into the goal desk
Step 1: Extract and cleanse knowledge from a supply system
As within the Sort-1 SCD sample, our first steps are to extract and cleanse knowledge from the supply system. Utilizing the identical strategy as above, we difficulty a federated question and persist the extracted knowledge to a desk in our staging schema:
Step 2: Evaluate to a dimension desk
With this knowledge landed, we are able to now examine it to our dimension desk so as to make any required knowledge modifications. The primary of those is to replace in place any information flagged as late arriving from prior truth desk ETL processes. Please notice that these updates are restricted to these information flagged as late arriving and the IsLateArriving flag is being reset with the replace in order that these information behave as regular Sort-2 SCDs transferring ahead:
Step 3: Expire versioned information
The subsequent set of information modifications is to run out any information that must be versioned. It’s essential that the EndDate worth we set for these matches the StartDate of the brand new report variations we’ll implement within the subsequent step. For that purpose, we’ll set a timestamp variable for use between these two steps:
NOTE: Relying on the info accessible to you, you might elect to make use of an EndDate worth originating from the supply system, at which level you wouldn’t essentially declare a variable as proven right here.
Please notice the extra standards used within the WHEN MATCHED clause. As a result of we’re solely performing one operation with this assertion, it might be attainable to maneuver this logic to the ON clause, however we stored it separated from the core matching logic, the place we’re matching to the present model of the dimension report for readability and maintainability.
As a part of this logic, we’re making heavy use of the equal_null() perform. This perform returns TRUE when the primary and second values are the identical or each NULL; in any other case, it returns FALSE. This offers an environment friendly option to search for modifications on a column-by-column foundation. For extra particulars on how Databricks helps NULL semantics, please discuss with this doc.
At this stage, any prior variations of information within the dimension desk which have expired have been end-dated.
Step 4: Insert new information
We will now insert new information, each really new and newly versioned:
As earlier than, this might have been applied utilizing an INSERT assertion, however the outcome is identical. With this assertion, we have now recognized any information within the staging desk that don’t have an unexpired corresponding report within the dimension tables. These information are merely inserted with a StartDate worth according to any expired information that will exist on this desk.
Subsequent steps: implementing the very fact desk ETL
With the scale applied and populated with knowledge, we are able to now give attention to the very fact tables. Within the subsequent weblog, we’ll exhibit how the ETL for these tables might be applied.
To be taught extra about Databricks SQL, go to our web site or learn the documentation. It’s also possible to take a look at the product tour for Databricks SQL. Suppose you need to migrate your present warehouse to a high-performance, serverless knowledge warehouse with a terrific person expertise and decrease whole value. In that case, Databricks SQL is the answer — strive it free of charge.