1

Topic: Timeout: level 300

There are complexities with  from.NET applications in runtime .
More in detail:
Once a day.NET application copies the fresh given data in archive basis which grew already to 4.
The archive basis lies on rather slow disk (one physical disk).
It  (on the slow carrier) 24 hours last.
For copying in archive basis in application opens SqlDataReader for a source, and it is transferred in object SqlBulkCopy for record in the archive destination table.
For SqlBulkCopy  properties NotifyAfter and BatchSize are adjusted.
it is possible to include transaction for all  in the data sheet (i.e. on ).
If it is ungeared,  UseInternalTransaction = true on SqlBulkCopy.
for SqlBulkCopy it is installed in 0.  for a source it is installed in 120 seconds
Till now all was normal.
From some time application started to take off on , if it is fulfilled simultaneously with  .
And  it is strange:
Some tables are copied bases of problems.
For others - in the core with considerable quantity BLOB of the data some is copied  lines, then seconds through 20 after the last record takes off .
At random:
Included asynchronous update of statistics for target basis - did not help.
Then still reduced BatchSize - did not help.
Then still included transaction - helped .
But there is absolutely not clear a reason .
. Who faced or has an explanation, I will be grateful.
: please, do not offer  iron - my question on the reasons.

2

Re: Timeout: level 300

Alexander Us wrote:

Since some time application started to take off on , if it is fulfilled simultaneously with  .

In process  it is minimum  operations  completely. Accordingly, runtime increases also.

3

Re: Timeout: level 300

invm wrote:

it is passed...
In process  it is minimum  operations  completely. Accordingly, runtime increases also.

the nobility  what basis is executed...

4

Re: Timeout: level 300

aleks222 wrote:

the nobility  what basis is executed by Isho...

Full is fulfilled  target basis - bases of archive.

5

Re: Timeout: level 300

invm wrote:

In process  it is minimum  operations  completely. Accordingly, runtime increases also.

Thanks for specification.
Unfortunately it does not change a pattern - setting  for a source 120, for the purpose 0,
In the beginning writes some units of records, then takes off approximately through 20 (it ) second after one (casual) them them.
And when  at record level in the table (day import) already 2 times as fulfilled transaction without .

6

Re: Timeout: level 300

Alexander Us wrote:

it is passed...
Full is fulfilled  target basis - bases of archive.

Well so, alternate  and wonderful application.
Days in a day.

7

Re: Timeout: level 300

aleks222 wrote:

Well so, alternate  and wonderful application. Days in a day.

Type "it is necessary to hammer in curve nails curve hammers"?
I wrote, I want to understand the reason .

8

Re: Timeout: level 300

Alexander Us wrote:

it is passed...
Type "it is necessary to hammer in curve nails curve hammers"?
I wrote, I want to understand the reason .

And what here ?
"exterior ", is "internal " the server.
https://docs.microsoft.com/en-us/sql/t- … erver-2017
I.e. if something cannot get access to a resource for 20  is is killed with an error.
If you attend to an output of error MS SQL in the application - it becomes more clear.
Well, or  catch.

9

Re: Timeout: level 300

aleks222 wrote:

Okromja "exterior ", is "internal " the server.
https://docs.microsoft.com/en-us/sql/t- … er-2017...

value @@ LOCK_TIMEOUT for  on target basis.
Produces-1
Can eat still other parameters for internal ?

10

Re: Timeout: level 300

Alexander Us;
Session waitings analyze - sys.dm_exec_session_wait_stats
If the version does not allow, through extended events - https://blog.sqlauthority.com/2016/05/2 … wait_info/

11

Re: Timeout: level 300

invm;
Thanks big, I will dig.
But can eat parameters,  influence time  sessions?
Whether them at once it can is possible will twist and look at effect?

12

Re: Timeout: level 300

Alexander Us;
I put a hedgehog that sql here there is nothing

13

Re: Timeout: level 300

Alexander Us wrote:

it is passed...
value @@ LOCK_TIMEOUT for  on target basis.
Produces-1
Can eat still other parameters for internal ?

Shame, Watson.

14

Re: Timeout: level 300

https://msdn.microsoft.com/ru-ru/librar … opytimeout (v=vs.110).aspx

15

Re: Timeout: level 300

aleks222 wrote:

the Shame, Watson.

Holmes well you with yours , what you was specific mean?
And as to SqlBulkCopy:
"Value 0 means absence of restrictions. Bulk copy operation will be in wait state infinitely long."
I know it, and is installed, I wrote.
Or I that viewed that important?