Standardisation of DataMart View Queries for SQL OnDemand To enhance query consistency and readiness for SQL OnDemand, we have implemented a major standardisation across all DataMart view queries. Key Enhancements: ✅ Uniform Aliases for Data Sources – All table references now include consistent and meaningful aliases, improving readability and maintainability. ✅ Standard Positioning of — … Read more
This draft framework provides a robust SLA for DataMart availability, balancing business needs, technical feasibility, and stakeholder communication. 1. Availability Target Set a clear uptime percentage that aligns with the criticality of the DataMart to your business processes. 2. Operational Hours Define the expected operational hours of the DataMart. Specify if it needs to be … Read more
Microsoft Fabric is designed to integrate multiple analytics workloads, including data engineering, data science, and business intelligence, within a unified platform. While our current Medallion structure already has a logical progression of data refinement (Bronze → Silver → Gold), there are key differences in architecture, tooling, and approach that we might consider while emulating a … Read more
Purpose The Customer Invoice Item data mart is designed to provide detailed insights into invoice-level transactional data for customers. It organises, validates, and enriches raw data from the source system into a structured and accessible format, enabling comprehensive analysis and reporting. Use Case Owner: Soon Tan Typical Use Case: Style: Fact, Each row represents a unique Invoice … Read more
An interim release with no functional changes Notes 1. 🔴 MISSING IN PRD CONTAINER: customer_details_CAD.sql2. ⚠️ DIFFERENT: customer_details.sql3. ⚠️ DIFFERENT: project_cost_CAD.sql4. ⚠️ DIFFERENT: project_details_plus_CAD.sql5. ⚠️ DIFFERENT: project_details_CAD.sql6. ⚠️ DIFFERENT: project_revenue_CAD.sql Total number of different files: 5Total number of missing files in DEV CONTAINER: 0Total number of missing files in PRD CONTAINER: 1
Notes 1. ⚠️ DIFFERENT: project_cost_CAD.sql2. ⚠️ DIFFERENT: project_cost_USD.sql3. ⚠️ DIFFERENT: project_details_CAD.sql4. ⚠️ DIFFERENT: project_details_plus_CAD.sql5. ⚠️ DIFFERENT: project_details_plus_USD.sql6. ⚠️ DIFFERENT: project_details_USD.sql7. ⚠️ DIFFERENT: project_revenue_CAD.sql8. ⚠️ DIFFERENT: project_revenue_USD.sql Total number of different files: 8Total number of missing files in DEV CONTAINER: 0Total number of missing files in PRD CONTAINER: 0
Additions Employee.Absence This view combines employee data (DIM_EMPLOYEE_OL) with absence details (QFACT_ABSENCE_DETAILS_OL$) to facilitate the creation of a dataset used for tracking and analysing employee absences in detail. It generates structured JSON data for efficient reporting, compliance, and analytical purposes. Employee.AbsenceLimit This view creates a structured dataset for tracking and analysing employee absence limits. It … Read more
Purpose The Global Foreign Exchange Rate view provides a structured dataset for analysing currency exchange rates relative to the British Pound (GBP) as the base currency. This view supports financial and operational use cases requiring reliable exchange rate data for reporting and analytics. Use Case Source DataMart Integration There are no DataMart identifiers Sample Exec … Read more
Purpose This view creates a structured dataset for tracking and analysing employee absence limits. It links employee details (DIM_EMPLOYEE_OL) with their corresponding absence limit information (QFACT_ABSENCE_LIMIT_OVERVI_OL$), presenting the data in JSON format for improved integration and usability. Use Case Owner: Luisa WinderTypical Use Case: Style: Fact, Each row represents a unique Employee Limit Seq with … Read more
Purpose This view combines employee data (DIM_EMPLOYEE_OL) with absence details (QFACT_ABSENCE_DETAILS_OL$) to facilitate the creation of a dataset used for tracking and analysing employee absences in detail. It generates structured JSON data for efficient reporting, compliance, and analytical purposes. Use Case Owner: Luisa WinderTypical Use Case: Style: Fact, Each row represents a unique Employee Absence Seq with … Read more