Step 1: Log into azure portal
Step 2: Click “Browse” and look for HDInsight Clusters which will have Hadoop icon.
Step 3: Click the HDInsight Clusters and “Add” a new cluster.
Step 4: Provide the cluster name and other details as like below and cluster type should be “Hadoop”.
Step 5: Cluster credentials are mandatory so define the credentials. In this section, you can enable remote desktop by selecting “YES”, need to provide remote desktop credentials.
Step 6: Datasource must be configured for cluster.
Step 7: Node pricing tiers is required to configure as like below.
Step 8: Click the create button when all the steps are filled and configured. HDInsight cluster will be created and deployed for your use.
We discussed about preparing datasets using files from different environment (Local drive & OneDrive) in my previous articles. Go through here.
We have another option under files section which is “SharePoint – Team Sites”.
It is very easy to get a file (dataset) from SharePoint as we are using business email to connect Power BI so no need to provide the credentials again.
Select the file from SharePoint and connect to Power BI. File will be added in to Datasets.
In my last article, we discussed about how to prepare a dataset from local file.
This article speaks about how we can create a dataset which is stored in OneDrive. It can be personal or business OneDrive.
There is no changes up to 4th step from my previous article, after that follow the below steps
As we discussed the levels in Power BI, the first level is creating dataset.
To start prepare the dataset, first sign in to the power BI here,
This article will talk about, how to create a dataset from local file.
Steps to import the local file,
Microsoft SQL Server 2016 has one of the exciting feature called PolyBase. It is acts as a bridge between relational database and Hadoop.
We can access all structured, unstructured and semi-structured data using known language of SQL.
Polybase allows user to use T-SQL Statements in Microsoft SQL Server Management studio to access data stored in Hadoop or Microsoft Azure blob storage.
Below services should up and running to use this feature.
To check the installed services in system,
Go through my previous article here, about Data storage format in columnstore Index.
There are lots of improvements in Query processing speed when we use columnstore Index.
Temporal is a database feature that was introduced in ANSI SQL 2011 and this is now supported in SQL Server 2016.
It is a new type of user defined table and designed to keep track of all historical changes on the table and make easy to do point in time analysis.
Main reasons to use temporal table,
Prerequisites to create temporal table,
Syntax to create Temporal Table
CREATE TABLE <Table Name>
<column 1> int NOT NULL PRIMARY KEY CLUSTERED
,<column 2> <datatype>
, <column n>
, [ValidFrom] datetime2 (2) GENERATED ALWAYS AS ROW START
, [ValidTo] datetime2 (2) GENERATED ALWAYS AS ROW END
, PERIOD FOR SYSTEM_TIME (ValidFrom, ValidTo)
WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = <schema>.<tablename> –Optional));
We can give any name instead of ValidFrom and ValidTo, both should be bind in PERIOD.