Microsoft Fabric (Azure Synapse, Data Engineering, etc.)

External Article

Getting Started with Azure SQL Data Warehouse - Part 4

  • Article

Azure SQL Data Warehouse is a new enterprise-class, elastic petabyte-scale, data warehouse service. Join Arshad Ali as he discusses round-robin and distributed tables, and how to create them. He also discusses how partitioning works in SQL Data Warehouse and looks at the impact of choosing the right distribution key. As a bonus Arshad shows you how to leverage PolyBase to quickly and easily import or export data from SQL Data Warehouse.

2017-05-25

3,392 reads

External Article

Getting Started with Azure SQL Data Warehouse - Part 3

  • Article

Microsoft introduced Azure SQL Data Warehouse, a new enterprise-class, elastic petabyte-scale, data warehouse service that can scale according to organizational demands in just few minutes. In this article, Arshad Ali discusses the different types of tables you can create in SQL Data Warehouse, how they impact performance and the best practices around them.

2017-04-28

3,633 reads

Blogs

“We love to debate minutiae”

By

I am guilty as charged. The quote was in reference to how people argue...

Advice I Like: Knots

By

Learn how to tie a bowline knot. Practice in the dark. With one hand....

Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency

By

As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...

Read the latest Blogs

Forums

Windows logins for users migrated from DomainA to DomainB

By a.koopman

Hi, I have a SQL Server instance where users connect to via Windows Authentication,...

Multiple Deployment Processes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Deployment Processes

How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases

By Kunal Rathi

Comments posted to this topic are about the item How to Use sqlpackage to...

Visit the forum

Question of the Day

Upgrading Admin Queries

I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?  

See possible answers