Low A Profile — Series Analysis of Low Drives The Low A profile is the classic team player — someone who naturally seeks alignment, inclusion, and the success of the group as a whole. This drive is characterised by cooperation, collaboration, and a desire for harmony. A Low A wants to contribute meaningfully, support others, … Read more
High D Profile — Series Analysis of High Drives As a child, you may have been the one endlessly asking “Why?”. As an adult, you look for context, background, and depth. Detail matters. Accuracy matters. And phrases such as “the devil is in the details” or Wyatt Earp’s “fast is fine, but accuracy is everything” … Read more
High C Profile — Series Analysis of High Drives “He who fails to plan is planning to fail.”“I spend more time with colleagues than some members of my family — shouldn’t I get to know them better?” Both statements capture the essence of the High C profile: confidence is rooted in structured process and meaningful … Read more
High B Profile — Analysis of High Drives Do you like this idea?Is this the right decision?Are we OK? Questions like these reveal something essential about the High B profile: self-confidence is shaped through valued relationships. For those with a High B drive, the opinions, reactions, and emotional cues of the people around them play … Read more
High A Profile — Series Analysis How do you know when you’ve done a good job? It sounds like a simple question, yet the answer often reveals something deeper about how we are naturally wired. For some people, a sense of achievement emerges when a manager expresses appreciation, when colleagues offer praise, or when an … Read more
Overview The cdm_Archive_to_STG notebook is a critical component in the cdm_today and cdm_Archive pipeline. Its primary role is to create a staging table that represents a point-in-time snapshot of source data, which is then used by the cdm__Archive_upsert notebook to accurately update the main dimension table. This staging layer acts as a buffer between raw … Read more
Overview The myOSH_To_Bronze notebook is designed to handle multiple MyOSH API endpoints dynamically, meaning it can process different endpoints such as records or users without hardcoding logic. For most endpoints (like users), the process is straightforward: it performs a regular API call and writes the response directly to JSON in the source container and to … Read more
Overview The myosh_Archive notebook is designed to maintain a complete and accurate archive of records from the MyOSH API. It ensures that no data is lost by identifying gaps in the current API response and backfilling missing records, then merging everything into a single, consolidated archive stored in the Azure Data Lake container. Why Do … Read more
Overview The cdm__Archive_upsert notebook is designed to help keep accurate historical records of data. It implements a technique called Slowly Changing Dimension Type 2 (SCD2), which means instead of overwriting old information, it creates a timeline of changes so you can see what was true at any point in time. This method ensures that previous … Read more
When working with Microsoft Fabric, one common challenge is keeping the SQL endpoint in sync with the Lakehouse endpoint after a pipeline run. Fabric provides two endpoints for every Lakehouse: Why does the SQL endpoint sometimes lag? The SQL endpoint doesn’t automatically refresh its metadata the moment new data lands in the Lakehouse. Instead, a … Read more