Azure SQL Data Warehouse – First Notes
I finished my super busy week with many excited and positive information:
- Good signature for big cloudification project with huge customer. Thank you (Thang Bui, Viet Pham and Quang Nguyen) for my new experience in this domain.
- The approval to start review Azure SQL Data Warehouse from Microsoft.
Cloudification is my job now, it’s confidential and cannot be shared at this moment. So in this article, I will share my first feeling of SQL Data Warehouse only. I hope this information can bring something helpful to you.
- Fast (it takes about 15 minutes) and easy (few steps) to initiate new SQL Data Warehouse resource;
- Good performance and cheap price. The smallest option is 100 DWU can provide the capability to scan 1B rows in 279 seconds with the price at $0.7 per hour. That cool;
- Azure SQL Data Warehouse doesn’t support old SQL Database servers. It’s the first limitation I found;
- Almost of regions already supported, including US, Europe, Southeast Asia and Japan;
- Supports to integrate with PowerBI and Visual Studio 2013 (I’m using VS 2015 so need to prepare new VM to review VS integration feature later);
- Supports to create Data Warehouse with sample database (AdventureWork database). It’s good enough for some one to study;
- Easy to scale up or down by changing DWU option;
- Support up to 10TB, it’s good enough for almost of Data Warehouse;
- Robust auditing and integrate with Azure storage account;
- Data protection (data encryption) is built-in feature;
- Supports to integrate with multiple programming languages;
- Built-in monitoring to show DWU usage, storage information and query activity;
From my perspective, Azure SQL Data Warehouse is good service and I’ll have other articles to discuss about it in more detailed level.