Azure Security Defenses you ought to know AND Hand-On session on Azure Data Factory

Azure Security Defenses you ought to know AND Hand-On session on Azure Data Factory

        Please join me (Nik- Shahriar Nikkhah) and Deepack Kaushik on new webinar on “Azure Security Strategies you ought to know and Introducing Azure Data Factory”. 

Sat, Jan 26, 2019 8:00 AM – 10:00 PM CST (Saskatchewan Time) 

Price: Free of cost 

Event URL: https://global.gotomeeting.com/join/144831997

Note: There are 250 seats only. First come first serve. 

Agenda:Azure Security Defenses you ought to know 

• Why Cloud Security is different & better.
• Azure Security Center
• Confidentiality. Integrity. Availability. (CIA)
• Advanced Threat Protection: for your data

Introducing Azure Data Factory (HAND-ON Session-Demo)

• What is Azure Data Factory (ADF)?
• Looking at ADF from a Farm perspective.
• How to build Pipeline Framework
• How to build ADF Framework
• Dynamic ADF Pipeline
• ADF and External Services (ALA)

Azure Security Strategies you ought to know	Deepak Kaushik	08:00 AM – 09:00 AM
Introducing Azure Data Factory	Shahriar Nikkhah	09:00 AM – 10:00 AM

 Session details are as follows, 

Webinar: Azure Security Defenses you ought to know AND Hand-On session on Azure Data Factory 
Sat, Jan 26, 2019 8:00 AM – 10:00 AM PST 

Please join my meeting from your computer, tablet or smartphone. 
https://global.gotomeeting.com/join/144831997

You can also dial in using your phone. 
Canada: +1 (647) 497-9391

Access Code: 144-831-997 

First GoToMeeting? Let’s do a quick system check:
https://link.gotomeeting.com/system-check

Speaking at Data Platform Saturday at Microsoft Toronto. Saturday 28th of May, 2016

Main Topic: Power Bi Presentation
Topics: Power BI, Big data , M Language, DAX

Posted By: Nik - Shahriar Nikkhah April 26, 2016

I will be speaking at the "Data Platform Saturday" at Microsoft Toronto Canada. Saturday 28th of May, 2016, Link to the event

Main focus will be on Power BI and o365 (Intermediate level)

Outline:

• Environment ready with O365 + Power BI, (Step by step installation)
• Power BI Desktop
• M Language
• Using DAX
• Visualization portal in Power BI
• Data relations and data issues in Power BI

Adding Age Banding to your Power BI Desktop

Topics: Power BI, Big data , M Language

Posted By: Nik - Shahriar Nikkhah January 24, 2016

You may have an age banding dimension (DimAgeBand) in your BI world, your biggest challenge will be adding new age band to the current dimension dynamically with the minimum amount of changes.

Age Banding Overview

Grouping an age range is basically called "Age Banding", every business or analysts looks at the age banding dimension form a different angle (or point of view), they like to analyze the age in different groups or [AgeBand].

In your DimAgeBand-ing you will have an [Age] or [AgeID] field that will play the role of your unique key and other fields that represents the business requirement like [AgeBand1] and [AgeBand2].

Top 20 and bottom 20 records.

The Code In M Language

Use the mentioned M Language code in a "Blank Query" in Power BI to define the business age band.


--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---

let
    // Make an Age Range, Max number is 127 records else if needed more records you must change the data type from Int8 to Int16
    Source = {-1.. 127},
    // Convert List to table
    ConvertedToTable = Table.FromList(Source, Splitter.SplitByNothing(), null, null, ExtraValues.Error),
    // Rename field to [Age]
    RenamedColumns = Table.RenameColumns(ConvertedToTable,{{"Column1", "Age"}}),
    // Change the data type of the field [Age] to Int8 (-127 ... +127)
    ChangeDataType= Table.TransformColumnTypes(RenamedColumns ,{{"Age", Int8.Type}}),
    // Add AgeBand1
    AddedAgeBand1Column = Table.AddColumn(ChangeDataType, "AgeBand1", each
  if   -1 = [Age] then "Unknown"
  else if   0 <= [Age] and [Age] <   18 then "Under 18"
  else if  18 <= [Age] and [Age] <=  24 then "[18-24]"
  else if  25 <= [Age] and [Age] <=  34 then "[25-34]"
  else if  35 <= [Age] and [Age] <=  44 then "[35-44]"
  else if  45 <= [Age] and [Age] <=  54 then "[45-54]"
  else if  55 <= [Age] and [Age] <=  64 then "[55-64]"
  else if  65 <= [Age] and [Age] <=  74 then "[65-74]"
  else if  75 <= [Age] and [Age] <=  84 then "[75-84]"
  else if  85 <= [Age] and [Age] <=  94 then "[85-94]"
  else if  95 <= [Age] and [Age] <= 104 then "[95-104]"
  else if 105 <= [Age] and [Age] <= 114 then "[105-114]"
  else if 115 <= [Age] and [Age] <= 124 then "[115-124]"
  else "[125 +"),
    // Add AgeBand2
    AddedAgeBand2Column = Table.AddColumn(AddedAgeBand1Column, "AgeBand2", each
  if   -1 = [Age] then "Unknown"
  else if   0 <= [Age] and [Age] <   20 then "Under 20"
  else if  20 <= [Age] and [Age] <=  29 then "[20-29]"
  else if  30 <= [Age] and [Age] <=  39 then "[30-39]"
  else if  40 <= [Age] and [Age] <=  49 then "[40-49]"
  else if  50 <= [Age] and [Age] <=  59 then "[50-59]"
  else if  60 <= [Age] and [Age] <=  69 then "[60-69]"
  else if  70 <= [Age] and [Age] <=  79 then "[70-79]"
  else if  80 <= [Age] and [Age] <=  89 then "[80-89]"
  else if  90 <= [Age] and [Age] <=  99 then "[90-99]"
  else if 100 <= [Age] and [Age] <= 109 then "[100-109]"
  else if 110 <= [Age] and [Age] <= 119 then "[110-119]"
  else "[120 +")
in
    AddedAgeBand2Column
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---

What was so Dynamic?

In the above M code you can add new age banding [AgeBand3] as required by the business, without changing anything in your Power BI.

Reference

https://powerbi.microsoft.com/en-us/