Implementing a Dimensional Knowledge Warehouse with Databricks SQL: Half 2

As organizations consolidate analytics workloads to Databricks, they usually must adapt conventional information warehouse strategies. This collection explores implement dimensional modeling—particularly, star schemas—on Databricks. The primary weblog centered on schema design. This weblog walks by means of ETL pipelines for dimension tables, together with Slowly Altering Dimensions (SCD) Sort-1 and Sort-2 patterns. The final weblog will present you construct ETL pipelines for reality tables.

Slowly Altering Dimensions (SCD)

Within the final weblog, we outlined our star schema, together with a reality desk and its associated dimensions.  We highlighted one dimension desk particularly, DimCustomer, as proven right here (with some attributes eliminated to preserve house):

The final three fields on this desk, i.e., StartDate, EndDate and IsLateArriving, symbolize 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 wish to create new information for that buyer in order that details corresponding to our on-line gross sales transactions in FactInternetSales are related to the precise 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 precise model.  

NOTE: As a result of the surrogate key’s generally used to hyperlink details and dimensions, dimension tables are sometimes clustered based mostly on this key. Not like conventional relational databases that make the most of b-tree indexes on sorted information, Databricks implements a novel clustering technique generally known as liquid clustering. Whereas the specifics of liquid clustering are exterior the scope of this weblog, we persistently use the CLUSTER BY clause on the surrogate key of our dimension tables throughout their definition to leverage this characteristic successfully.

This sample of versioning dimension information as attributes change is called the Sort-2 Slowly Altering Dimension (or just Sort-2 SCD) sample. The Sort-2 SCD sample is most popular for recording dimension information within the basic dimensional methodology. Nonetheless, there are different methods to cope with adjustments in dimension information.

One of the crucial frequent methods to cope with altering dimension values is to replace current information in place.  Just one model of the document is ever created, in order that the enterprise key stays the distinctive identifier for the document.  For numerous causes, not the least of that are efficiency and consistency, we nonetheless implement a surrogate key and hyperlink our reality information to those dimensions on these keys. Nonetheless, the StartDate and EndDate metadata fields that describe the time intervals over which a given dimension document is taken into account lively usually are not wanted. This is called the Sort-1 SCD sample.  The Promotion dimension in our star schema offers a superb instance of a Sort-1 dimension desk implementation:

However what in regards to 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 document is one for which the enterprise key exhibits up throughout a reality ETL cycle, however there is no such thing as a document for that key situated throughout prior dimension processing.  Within the case of the Sort-2 SCDs, this subject is used to indicate that when the information for a late arriving document is first noticed in a dimension ETL cycle, the document needs 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 document will likely 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 essentially the most continuously carried out of those patterns and the strategies used with the others are intently associated to what’s employed with these, we’re limiting this weblog to simply these two dimension varieties. For extra details about the eight kinds of SCDs acknowledged by the Kimball Group, please see the Slowly Altering Dimension Strategies part of this doc.

Implementing the Sort-1 SCD Sample

With information being up to date in place, the Sort-1 SCD workflow sample is essentially the most easy of the two-dimensional ETL patterns. To help these kinds of dimensions, we merely:

1. Extract the required information from our operational system(s)
2. Carry out any required information cleaning operations
3. Examine our incoming information to these already within the dimension desk
4. Replace any current information the place incoming attributes differ from what’s already recorded
5. Insert any incoming information that shouldn’t have a corresponding document within the dimension desk

As an instance a Sort-1 SCD implementation, we’ll outline the ETL for the continued inhabitants of the DimPromotion desk.

Step 1: Extract information from an operational system

Our first step is to extract the information from our operational system.  As our information warehouse is patterned after the AdventureWorksDW pattern database offered by Microsoft, we’re utilizing the intently 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 house), with the question outcomes endured in a desk in our staging schema (that’s made accessible solely to the information engineers in our surroundings by means of permission settings not proven right here). That is however considered one of some ways we are able to entry supply system information on this surroundings:

Step 2: Examine incoming information to these within the desk

Assuming we’ve no extra information 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 information replace/insert operations in a single step utilizing a MERGE assertion, matching our staged information and dimension information on the enterprise key:

One vital factor to notice in regards to the assertion, because it’s been written right here, is that we replace any current information when a match is discovered between the staged and printed dimension desk information. We might add extra standards to the WHEN MATCHED clause to restrict updates to these cases when a document in staging has totally 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 information.)

The Sort-2 SCD sample

The Sort-2 SCD sample is a little more advanced. To help these kinds of dimensions, we should:

1. Extract the required information from our operational system(s)
2. Carry out any required information cleaning operations
3. Replace any late-arriving member information within the goal desk
4. Expire any current information within the goal desk for which new variations are present in staging
5. Insert any new (or new variations) of information into the goal desk

Step 1: Extract and cleanse information from a supply system

As within the Sort-1 SCD sample, our first steps are to extract and cleanse information from the supply system.  Utilizing the identical method as above, we difficulty a federated question and persist the extracted information to a desk in our staging schema:

Step 2: Examine to a dimension desk

With this information landed, we are able to now evaluate it to our dimension desk with a view to make any required information modifications.  The primary of those is to replace in place any information flagged as late arriving from prior reality desk ETL processes.  Please word 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 vital that the EndDate worth we set for these matches the StartDate of the brand new document variations we’ll implement within the subsequent step.  For that motive, we’ll set a timestamp variable for use between these two steps:

NOTE: Relying on the information accessible to you, it’s possible you’ll 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 word 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 potential 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 document 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 solution to search for adjustments on a column-by-column foundation.  For extra particulars on how Databricks helps NULL semantics, please consult 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 carried out utilizing an INSERT assertion, however the consequence is identical.  With this assertion, we’ve recognized any information within the staging desk that don’t have an unexpired corresponding document within the dimension tables. These information are merely inserted with a StartDate worth in line with any expired information which will exist on this desk.

Subsequent steps: implementing the very fact desk ETL

With the scale carried out and populated with information, we are able to now give attention to the very fact tables. Within the subsequent weblog, we’ll display how the ETL for these tables may be carried out.

To study 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 wish to migrate your current warehouse to a high-performance, serverless information warehouse with an ideal consumer expertise and decrease whole price. In that case, Databricks SQL is the answer — attempt it totally free.