Viewing 9 posts - 1 through 9 (of 9 total)
Hi,
I could solve the problem. Inside the subselect there was an inline function which prevent the parallel processing. I put this function in front of the insert into a variable...
April 24, 2014 at 2:42 am
No, there aren"t any other indices
April 23, 2014 at 11:29 pm
But can you explain me why a parallel insert and delete in two different Partition works meanwhile a parallel insert in the Same partitions will be blocked ?
This behaviour should...
April 23, 2014 at 12:03 pm
Hi,
the listed insert statement is only an example. The mentioned subselect is in reality more complex. So I've only simplified it.
Yes perhaps it could work over the indirect way...
April 23, 2014 at 8:24 am
Hi,
thanks a lot for your tips. I've decided to change the sequence of the jobs of each parallel process, so I could also minimize the locks.
But I have still...
April 22, 2014 at 4:59 am
I think this solution doesn't help me. Because a switch partition leads to a Schema-M lock. And if all of my parallel processes wants a schema-m lock nothing works anymore.
I...
April 17, 2014 at 7:43 am
Hi,
most of the tables are partionend by our StoreId. In sum we have 6 stores (1,2,...6), so 6 partitions per table. And all our stored procedures have a input-parameter StoreId...
April 17, 2014 at 6:34 am
Yes you're right. The most locks occur by the merge statements. Do you have an idea how to prevent it?
So can you also give me some hints what i have...
April 17, 2014 at 3:39 am
Hi Koen,
thanks for the fast answer. But is there no other chance to load the table at the same time? Because i thought that because of the partioned tables that...
April 17, 2014 at 3:23 am
Viewing 9 posts - 1 through 9 (of 9 total)