392 reputation
313
bio website endforward.nl
location Amsterdam, Netherlands
age 30
visits member for 3 years, 3 months
seen Mar 7 at 13:20
.net developer with interest in c#, faceted navigation (solr), distributed systems, wcf, xslt, umbraco, asp.net mvc and some other things...

Feb
7
awarded  Notable Question
Nov
17
awarded  Popular Question
Sep
30
awarded  Notable Question
Sep
26
asked How to insert and or update a variable number of records and prevent concurrency issues
Jun
21
awarded  Popular Question
Mar
14
awarded  Popular Question
Oct
11
awarded  Popular Question
Sep
4
asked How to remove xmlns from child elements with FOR XML
Jun
14
comment How to prevent daily index fragmentation of 99%
I am rebuilding every day right now but I wonder if I can prevent this from having to happen every day since I can anticipate pretty well on how the data evolves.
Jun
14
revised How to prevent daily index fragmentation of 99%
added 878 characters in body
Jun
14
asked How to prevent daily index fragmentation of 99%
Jan
24
accepted What affects the speed of a count(*) besides the number of records
Jan
24
asked What affects the speed of a count(*) besides the number of records
Jan
16
comment What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
I ended up going with the snapshot isolation level. The batched approach also worked but I got very random performance out of it and sometimes over 1000% worse.
Jan
16
accepted What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
Jan
14
awarded  Commentator
Jan
14
comment What are the disadvantage/consequences of moving updated column to separate table to prevent table lock on the original table?
I am reading up on both options.
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.