The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

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.

the only alternative would be to ~store~ the results of the calculation, which seems rather safe to do, once the scores for each round have been entered (if a score needs to be revised, then of course the calculated score would also need to be revised)

but the calculations take only a few nanoseconds, right? so where's the pain?

You could write a User Defined Function to help the query engine here, but that probably won't materially effect things unless you are talking lots and lots of data. More data than one would probably touch in a web app.

I am actually going through some old .net code and taking places that had alot of c#.net while, and for loops and rewriting the sql to remove those loops and eleviate alot of the webserver stress and in stead put it onto the db server. While doing this i wanted to make sure that every sql statment i made was as efficient as i could make it that way i would not have to revisit it anytime soon.