Technical Article

Understanding and Controlling Parallel Query Processing in SQL Server

Data warehousing and general reporting applications tend to be CPU intensive because they need to read and process a large number of rows. To facilitate quick data processing for queries that touch a large amount of data, Microsoft SQL Server exploits the power of multiple logical processors to provide parallel query processing operations such as parallel scans. Through extensive testing, we have learned that, for most large queries that are executed in a parallel fashion, SQL Server can deliver linear or nearly linear response time speedup as the number of logical processors increases. However, some queries in high parallelism scenarios perform suboptimally. There are also some parallelism issues that can occur in a multi-user parallel query workload. This white paper describes parallel performance problems you might encounter when you run such queries and workloads, and it explains why these issues occur. In addition, it presents how data warehouse developers can detect these issues, and how they can work around them or mitigate them.

Blogs

Moving On-Prem PostgreSQL to the Cloud: Picking the Right Path for Big Tables

By

Every PostgreSQL migration eventually hits the same fork in the road. The database is...

A Spread of Vacation

By

I’m off on vacation today. Which is a little weird as I just got...

How AgentDBA Identifies Backup Failures

By

Every DBA has a box like this. Sitting untouched for months. Nobody’s proud of...

Read the latest Blogs

Forums

Calculating Geometric Mean in Power BI

By Dinesh Asanka

Comments posted to this topic are about the item Calculating Geometric Mean in Power...

TempDB Facts I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item TempDB Facts I

Have you done a Mid year check in?

By Pat Wright

Comments posted to this topic are about the item Have you done a Mid...

Visit the forum

Question of the Day

TempDB Facts I

Can I set Accelerated Database Recovery on tempdb?

See possible answers