402 reputation
415
bio website endforward.nl
location Amsterdam, Netherlands
age 31
visits member for 3 years, 11 months
seen Jun 24 at 11:06
.net developer with interest in c#, faceted navigation (solr), distributed systems, wcf, xslt, umbraco, asp.net mvc and some other things...

Jan
14
comment What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
I'll have to look into that, the calculation is quite simple it's comparing the value of columns in p to another table and then adding a number of points depending on whether they are <, = or >. The calculated points will not change over time for a row thats been calculated but there will be billions of records and 100's of millions that will be calculated in one go.
Jan
13
revised What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
edited title
Jan
13
comment What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
@JNK no that isn't necessary I can do that in the procedure that calculates the points.
Jan
13
comment What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
The table is locked because the number of rows/pages that are involved is so large that it is more efficient to lock the table
Jan
13
asked What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
Jan
12
comment why doesn't time for a simple update scale linearly with the number of records?
Marked this answer as correct since the problem was out of date statistics which was visible in the execution plan as a difference in nr of expected and actual rows.
Jan
11
comment why doesn't time for a simple update scale linearly with the number of records?
I am seeing a 800% difference in estimated rows and actual rows. I will update the statistics tomorrow (don't have the proper permission currently) and see if the problem persists and update the question accordingly.
Jan
11
comment why doesn't time for a simple update scale linearly with the number of records?
@ids contains the same 10 id's in both cases so the performance of the split function is equal.
Jan
11
revised why doesn't time for a simple update scale linearly with the number of records?
added some more information about the distribution of the data
Jan
11
revised why doesn't time for a simple update scale linearly with the number of records?
Added the update query
Jan
11
comment why doesn't time for a simple update scale linearly with the number of records?
Ok I will collect them and update the question with them. THanks so far.
Jan
11
asked why doesn't time for a simple update scale linearly with the number of records?
Jan
10
accepted Update column of a large set of records with a calculated value
Jan
6
awarded  Critic
Jan
6
asked Update column of a large set of records with a calculated value
Jan
3
awarded  Yearling
Nov
15
asked Pros and cons of having one table per entity vs. having a shared table with an extra column indicating the entity type
Nov
9
accepted How to prevent big performance impact during index creation
Nov
3
asked How to prevent big performance impact during index creation
Nov
2
accepted How can I monitor the call count per stored procedure per timespan?