Profile
Data is the most essential commodity for the next generation. I worked with the data for many sectors throughout my career. It amazes me how the data is getting extracted, transformed(cleansed) and Loaded into the powerful engines before being served to the next available customer. Often businessess never have the clear visibility into business. I use better resources and strategy to put all those pieces at your fingertips, so you can make the job faster, more effective decisions for your business.

Three Key element I always use to for better deliverance to all my clients.
Strategy - I always assess, plan and build a roadmap by begin with the end in mind.
Architecture - We as a partner will always discuss on for best approach to move to the cloud, modernise or scale the business solutions for the best approach towards visulasing the data.
Implementation - Several methods of implementing a high quality output through Microsoft PowerBI, Sql server data tools.

Workflows

Automation on Data

  1. Azure SQL- Cloud services, Azure SQL DB.
  2. Azure Analysis Services- AAS , MSOLAP

Data Development

  1. PowerBI- DAX Parameters.
  2. Power Query- ETL
  3. Integration Process- SSIS
  4. Analysis Process- MDX queries, Facts and Dimensions, KPI Indicators, Partitions,Aggregations.
  5. T-SQL- Joins, Keys, Performance tuning, Query Optimisation techniques, Index, Stored Procedures, Views, Triggers.

Apart from this, I am an ardent fan of books and failure. I read a book each week, fail each week and I always try to rejuvenate my work each day.

You can find me always here:

  




CDM folders and the Common Data Model

23-October-2019

Point #1: CDM is a metadata system

The Common Data Model is a metadata system that simplifies data management and application development by unifying data into a known form and applying structural and semantic consistency across multiple apps and deployments. If you’re coming from a SQL Server background, it may help to think about CDM as the “system tables” for data that’s stored in multiple locations and formats. This analogy doesn’t hold up to particularly close inspection, but it’s a decent place to start.

Point #2: CDM includes standard entity schemas

In addition to being a metadata system, the Common Data Model includes a set of standardized, extensible data schemas that Microsoft and its partners have published. This collection of predefined schemas includes entities, attributes, semantic metadata, and relationships. The schemas represent commonly used concepts and activities, such as Account and Campaign, to simplify the creation, aggregation, and analysis of data.

Point #3: CDM folders are data storage that use CDM metadata

A CDM folder is a folder in a data lake that conforms to specific, well-defined, and standardized metadata structures and self-describing data. These folders facilitate metadata discovery and interoperability between data producers and data consumers.

CDM folders store metadata in a model.json file; this is what makes them self-describing. This metadata conforms to the CDM metadata format, and can be read by any client application or code that knows how to work with CDM.

Point #4: You don’t need to use any standard entities 

The most common misconception I hear about CDM and CDM folders is that you only use them when you’re storing “standard data.” This is not correct. The data in a CDM entity may map to a standard entity schema, but for 99% of the entities I have built or used, this is not the case. There is nothing in CDM or CDM folders that requires you to use a standard schema.


WE ALWAYS WORK WITH :