1

Topic: Multisequencing, but not for all

Hi, All!
At collection   noted that application almost always makes serial plans. If to launch this request from studio, the plan normally turns out parallel. Why so? For someone parallel plans, and for someone serial? It somewhere is adjusted in a line of connection with the server? Or in configs of the server? How to look?

2

Re: Multisequencing, but not for all

V. Liseev, such it is possible to make... Through resource governor, but...  it is your case....

3

Re: Multisequencing, but not for all

https://blogs.msdn.microsoft.com/psssql … allelized/

4

Re: Multisequencing, but not for all

V. Liseev;
If it is not necessary MAXDOP 1 or  what thread  high there is a presence of resources for all it

5

Re: Multisequencing, but not for all

[V. Liseev] Hi, All!
At collection   noted that application almost always makes serial plans. If to launch this request from studio, the plan normally turns out parallel. Why so? For someone parallel plans, and for someone serial? It somewhere is adjusted in a line of connection with the server? [/quote]
It can depend from USER OPTIONS (see dbcc USER_OPTIONS ()).
Directly they parallelism not .
But the plan choice depends on them.
And possibility depends on the plan .

6

Re: Multisequencing, but not for all

TaPaK wrote:

V. Liseev;
If it is not necessary MAXDOP 1 or  what the thread  high there is a presence of resources for all it

Precisely is not necessary. Source codes of procedures are accessible in an open type. Both they one and those both for start by application, and for start manually.

7

Re: Multisequencing, but not for all

At me 2008 R2. Life - a pain. The hope is?

8

Re: Multisequencing, but not for all

V. Liseev;

wrote:

Precisely it is not necessary. Source codes of procedures are accessible in an open type.

and for the server?

wrote:

At me 2008 R2. Life - a pain. The hope is?

i.e. only digits in title  also did not read?

9

Re: Multisequencing, but not for all

TaPaK wrote:

V. Liseev;
it is passed...
And for the server?
it is passed...
I.e. only digits in title  also did not read?

There it is written by English on the white: [quote =] We did not have a good way to let customer know the reason until SQL 2012.
Starting a SQL Server 2012, XML showplan is enhanced to include the reason why the plan is not or cannot be parallelized.

I did not find in the plans of that is specified in article. Is not present NonParallelPlanReason at me. Even, if MAXDOP 1 explicitly to set.