If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > Rating - calculate or save

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-22-11, 10:05
amithev amithev is offline
Registered User
 
Join Date: Nov 2011
Posts: 6
Rating - calculate or save

Hi,

I'm developing a system where customers can rate Shops.
the question is, in a shop profile, when i want to show the numbers of products she sells and the average rating it got, do i need to query the rating table each time and calculate the data each time or should i save a field in the Shop table - RatingAverage which is update each time the shop is rated by some one.
The same question about the number of sells - save a counter that update each purchase - or query the deals (count the numbers of deals with the specific shop)?

which way is better?

thank's a lot

Amit
Reply With Quote
  #2 (permalink)  
Old 12-23-11, 04:48
amithev amithev is offline
Registered User
 
Join Date: Nov 2011
Posts: 6
help..

some one please?
Reply With Quote
  #3 (permalink)  
Old 12-23-11, 09:50
Wim Wim is offline
Registered User
 
Join Date: Nov 2004
Posts: 1,280
It depends.

When your site gets a lot of hits, you may want to speed these things up by storing those values in denormalised columns. Especially when you have a lot more reads than writes.

Denormalisation comes at a price, you must make sure those columns always contain the right values. But you could also take a more relaxed way, like saying: I will recalculate those values only every hour, or 15 minutes or so.
__________________
With kind regards . . . . . SQL Server 2000/2005/2008/2008 R2 Earned beers: 16
Wim
Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth
Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages
Reply With Quote
  #4 (permalink)  
Old 12-23-11, 11:44
amithev amithev is offline
Registered User
 
Join Date: Nov 2011
Posts: 6
thank you very much

you helped me
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On