Parallel Query Processing

* SQL Server provides parallel queries to optimize query execution and index operations for computers that have more than one microprocessor (CPU). Because SQL Server can perform a query or index operation in parallel by using several operating system threads, the operation can be completed quickly and efficiently.

* During query optimization, SQL Server looks for queries or index operations that might benefit from parallel execution.

* For these queries, SQL Server inserts exchange operators into the query execution plan to prepare the query for parallel execution. 

* An exchange operator is an operator in a query execution plan that provides process management, data redistribution, and flow control. The exchange operator includes the Distribute Streams, Repartition Streams, and Gather Streams logical operators as subtypes, one or more of which can appear in the Show plan output of a query plan for a parallel query.

* After exchange operators are inserted, the result is a parallel-query execution plan.

* A parallel-query execution plan can use more than one thread. A serial execution plan, used by a nonparallel query, uses only one thread for its execution. The actual number of threads used by a parallel query is determined at query plan execution initialization and is determined by the complexity of the plan and the degree of parallelism.

* Degree of parallelism determines the maximum number of CPUs that are being used; it does not mean the number of threads that are being used. The degree of parallelism value is set at the server level and can be modified by using the sp_configure system stored procedure.

* You can override this value for individual query or index statements by specifying the MAXDOP query hint or MAXDOP index option.

The SQL Server query optimizer does not use a parallel execution plan for a query if any one of the following conditions is true:
  • The serial execution cost of the query is not high enough to consider an alternative, parallel execution plan.
  • A serial execution plan is considered faster than any possible parallel execution plan for the particular query.
  • The query contains scalar or relational operators that cannot be run in parallel. Certain operators can cause a section of the query plan to run in serial mode, or the whole plan to run in serial mode.

To configure the max degree of parallelism option

  1. In Object Explorer, right-click a server and select Properties.
  2. Click the Advanced node.
  3. In the Max Degree of Parallelism box, select the maximum number of processors to use in parallel plan execution.

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read