Replicate Azure IaaS VMs

Microsoft has announced the public preview of disaster recovery for Azure IaaS virtual machines (VMs) using Azure Site Recovery (ASR). With this new capability of Azure Backup for IaaS VM, you can also protect IaaS based applications running on Azure by replicating on to different Azure regions.

Features highlights:

  • Offered “as-a-Service” – No need of additional infrastructure.
  • Simplified experience – Enables Cross-region DR.
  • Application-aware security – Control a fail over.
  • Non-disruptive DR drills





Azure SQL DW- Polybase

What is Polybase?

Polybase is a technology that accesses and combines both non-relational and relational data, all from within SQL Server. It allows you to run queries on external data in Hadoop or Azure blob storage.

  • It does not require to install additional software.
  • You can leverage T-SQL syntax for querying external data.
  • No knowledge about HADOOP or Azure is required.

PolyBase Scenarios:

  • Access data in Hadoop database with T-SQL.
  • Access Azure blob storage with T-SQL.
  • Import data from Hadoop or blobs as regular SQL Server tables.
  • Export data to Hadoop or Azure blob storage.
  • Integrate well BI tools – SSRS, SSAS, PowerPivot, PowerQuery, PowerView, Tableau, Microstrategy or Cognos.

PolyBase uses external tables to access data in Azure blob storage. Since data is not stored within Azure SQL DW, PolyBase handles authentication to external data by using a database-scoped credential.

Using PolyBase in Azure SQL DW Steps:

  • Create Master Key – to encrypt secret of your database scoped credential


  • Create Database Scoped Credential – to specify authentication information for your Azure storage account.

    IDENTITY = ‘polybasepoc’,
    SECRET = ‘secretkeygenerated’

  • Create External Data Source – to specify the location of your Azure blob storage.

    WITH (
    LOCATION = ‘wasbs://’,
    CREDENTIAL = AzureStorageCredential

  • Create External File Format – to specify the format of your data.

    WITH (

  • Create External Table – to specify the table definition and location of the data.

    [CC_ID] [nvarchar](50),
    [CC_CODE] [nvarchar](100),
    [CC_NAME] [nvarchar](100)
    WITH (

How to use?

select * from ExternalSource_CC

Limitations of Polybase:

  • PolyBase works with defined structure specified in External Table & File Format.
  • PolyBase does not allow to exclude Text Qualifiers.
  • PolyBase provides row number for failed records but does not give cell level failure information.
  • PolyBase does not recognize delimiter within data and in case delimiter is repeated in text, fails to read data.
  • Polybase only works with delimited text file, no other tabular format supported except Hadoop.
  • At present Polybase supports loading data files that have been UTF-8 encoded.


Azure SQL Data Warehouse – Pros & Cons

What is Azure SQL Data Warehouse?
Azure SQL Data Warehouse is PaaS based cloud solution for data storage. It is a massively parallel processing (MPP) cloud-based, scale-out, relational database capable of processing massive volumes of data.

Why you should consider moving to SQL Data Warehouse?
– Massively parallel processing solution. This makes queries many times faster than SQL DB.
– Combine relational data with cloud scale-out capabilities.
– Handles large volume data with massive storage. No storage limit.
– Processing power (compute) can be increase / decrease processing on one click within few seconds.
– Pause or resume DW on-demand, helps in cost saving when not in use.
– Supports SQL Server T-SQL language
– Platform as a service (PaaS) cloud based solution.
– Manages, detect and mitigate security threats Azure authentication features.
– High availability, gives you 99.9% up-time SLA in regions available to public.
– Built-in automated database backups.
– Minimal maintenance, reduced dependency on IT team.
– Good for OLAP environment.

Why you should not consider moving to SQL Data Warehouse?
– Supports SQL Server T-SQL language (not everything though).
– Supports only 32 concurrent connections.
– Supports only 1024 active connections.
– Does not support in-memory OLTP.
– Does not support CROSS database queries.
– Migration from on-premise or IaaS to SQL DW is a challenge.
– Blocking issues may take down entire Azure SQL DW.
– INSERT BULK API is not supported thoroughly.
– Not good for OLTP environment due to frequent changes.


Reference Link :-

Microsoft Codename “Atlanta” is on the way….

Today, database administrators (DBAs) have to spend a great deal of time and effort dealing with problems related to misconfiguration of Microsoft SQL Server. Microsoft Codename “Atlanta” is a configuration-monitoring cloud service that will help customers to reduce downtime and improve the performance of Microsoft SQL server deployments. This secure cloud service will help DBAs to:

  • Proactively avoid problems with Microsoft SQL Server through ongoing monitoring and alerting of configuration from the cloud
  • Reduce downtime and improve performance of Microsoft SQL Server through proactive scanning for known configuration issues and comparison with best practices.
  • Resolve issues faster by providing Microsoft, or your own support staff, the ability to get a current view of your configuration, changes that have been made, and use the most up to date solutions to solve them

As per Microsoft "Atlanta" is available by Nov 8, 2010 and the production version will be available by first half of 2011 calendar year. Currently "Atlanta" is available for US based datacenters.

Read more about Microsoft Codename "Atlanta" at…