294 reputation
28
bio website
location
age
visits member for 2 years, 6 months
seen Apr 7 at 9:23

Aug
12
accepted Should I add a column or 1-1 table if property is usualy null
Aug
11
asked Should I add a column or 1-1 table if property is usualy null
Jun
5
awarded  Good Question
May
21
awarded  Caucus
May
16
awarded  Yearling
Jan
31
accepted Is it OK to keep a value which updates in a table?
Jan
30
awarded  Custodian
Jan
30
reviewed Approve suggested edit on Is it OK to keep a value which updates in a table?
Jan
30
awarded  Popular Question
Jan
29
awarded  Nice Question
Jan
29
comment Is it OK to keep a value which updates in a table?
Ok the second comment made me understand, thanks
Jan
29
comment Is it OK to keep a value which updates in a table?
@JNK the way it is now - we do keep transactions and a total, so everything you mentioned can be tracked perfectly if needed, the Balance total is just to prevent us from recalculating the amount every action.
Jan
29
comment Is it OK to keep a value which updates in a table?
even if there may be 1000s of transactions? So i'll need to recompute it every time? can't it be a little hard on performance? can you add a little bit about why this is such a problem?
Jan
29
asked Is it OK to keep a value which updates in a table?
May
17
accepted performance issues when concurrent requests
May
17
awarded  Scholar
May
17
accepted Why is the following query so bad performance-wise
May
17
comment Why is the following query so bad performance-wise
Also, did you mean to have the @TempCardNumber in the inner query? it looks like it should just be 'select CardNumber From Cards Where CardNumber=@CardNumber UNION..."
May
17
comment Why is the following query so bad performance-wise
I guess this query intends to act as exists, after there is a check if TempCardNumber got the value of CardNumber...
May
17
asked Why is the following query so bad performance-wise