On Aug 16, 3:19 pm, "BruceM" wrote:
If you don't have a problem with storing a calculation in a base table, then
what is the normalization issue when it comes to queries? I doubt you are
arguing against normalization in base tables, but where are you trying to go
with this? How would you go about performing calculations? If the results
are stored in a table, something can be done to force recalculation as
needed, but what does that gain you?

It's true, I'm not very strict about normalization in base tables,
ditto VIEWs. Quite strict, though, because I require a good reason and
assurance of data integrity. But equally strict because both are
tables. Usually I have no good reason, consequently I make it a stored
proc.

I think those who are very strict about normalization in base tables
should be very strict about normalization in virtual tables.

But you know me: I think every table (including VIEWs) should have an
enterprise key defined by business rules; if the only unique
constraint is defined on a sole autonumber column then I wouldn't
consider the object to be a table!

Jamie.

--