Purpose Designed to display the output from the SharePoint List Change Request The myHistory version of the request is designed to evaluate the effectiveness of the change management process. Use Case Owner: Simon WillmoreTypical Use Case: Change Management Dashboard presents key metrics such as the number of open and closed change requestsStyle: Fact Dashboards Utilising … Read more
Data Source Identification: Data Ingestion and Storage: Data Staging: View Creation: Automated Deployment: Snapshot Creation and Storage:
When comparing the integration of CSV files and APIs with the DataWarehouse, several factors impact data integrity, including data accuracy, consistency, security, and the ability to handle large datasets. Below are some key comparisons and potential risks associated with each method: 1. Data Accuracy and Consistency CSV Integration: API Integration: 2. Data Security CSV Integration: … Read more
The procedure [cont].[upsert_bulk_meta_fields] is a SQL Server stored procedure designed for bulk upsert operations on metadata fields from source tables into a target metadata table. The procedure accepts various parameters to define the source and target tables, as well as the metadata structure, and supports batch processing. Key Steps in the Procedure: Purpose: The procedure … Read more
The SQL stored procedure [cont].[upsert_bulk_entity] is designed to handle the bulk insertion or updating (upserting) of entity data from a source table into a target entity table. Here’s a summary of the key steps involved: Overall, this procedure is designed to efficiently manage the bulk upsertion of entity data from a specified source to a … Read more
Alterations project_expenses update to code comment history Notes Files sql/svw/project/project_expenses.sql (DEV) and sql/svw/project/project_expenses.sql (PRD) are different
use masterCREATE LOGIN <user> use DatabaseCREATE USER <user> The EXECUTE permission was denied on the object ‘myhistory’, database ‘BMTDWHGLDB’, schema ‘get’. ALTER ROLE [exec_get] ADD MEMBER <user>;ALTER ROLE [read_hvw] ADD MEMBER <user>; DataSource.Error: Microsoft SQL: Error!! Error Number: 15151, Stored Procedure get_myHistory, Table Name: [hvw].[employee_details], Returned the following error : Cannot find the CREDENTIAL ‘https://bmtdwhuksstrprd.dfs.core.windows.net/gold/snapshot/employee/details/*.parquet’, … Read more
Stored Procedure Summary Purpose: This stored procedure, [get].[myhistory], is designed to retrieve historical views from a data mart for use in PowerBI analysis. It is flexible and allows users to specify various parameters to customise the view that is returned. Key Features: Typical Use Example Usage: PowerBI: Parameters:History_Host: bmt-dwh-uks-syn-prd-ondemand.sql.azuresynapse.netHistory_Endpoint: BMTDWHGLDBDataMart_Token: <my_token>
Purpose The Supplier Purchase Order Line Fact TableDesigned to display detailed quantitative data related to purchase orders from suppliers. This table integrates with various dimension tables to provide comprehensive insights into purchase order lines, including project associations, supplier details, and order statuses. The primary purpose is to support procurement tracking, cost analysis, and supplier management … Read more
Alterations Project.PurchaseOrderLine (&202407)ADD DEMAND CODE Project.SupplierInvoice (&202408)REMOVE WHERE filter src.DIM_COMPANY_ID not in (‘1062’) Additional Supplier.PurchaseOrderline Notes [‘Files 20240819/svw_dev_flat\\project_purchaseorderline.sql and 20240819/svw_prd_flat\\project_purchaseorderline.sql are different.’,‘Files 20240819/svw_dev_flat\\project_purchaseorderline_202407.sql and 20240819/svw_prd_flat\\project_purchaseorderline_202407.sql are different.’,‘Files 20240819/svw_dev_flat\\project_supplierinvoice.sql and 20240819/svw_prd_flat\\project_supplierinvoice.sql are different.’,‘File project_supplierinvoice_202408.sql found in 20240819/svw_dev_flat but not in 20240819/svw_prd_flat.’,‘File supplier_purchaseorderline.sql found in 20240819/svw_dev_flat but not in 20240819/svw_prd_flat.’]