Storing Massive Results

[jesus4u]

This is a sample of some data that is a result of a SELECT that calculates the total number of sites that referred traffic to our websites.

What I would like to do is store these results in another table so that my boss can simply SELECT that results table and get the report.

Is this good practice? I need your opinions.

Thanks

coralridge.org	52	4549	4549	0
-	36	3200	3199	1
216.247.64.85	5	499	499	0
65.240.226.68	1	97	97	0
crministries.org	0	84	84	0
google.com	0	43	43	0
search.yahoo.com	0	19	19	0
search.msn.com	0	16	16	0
oneplace.com	0	14	14	0

 

[Derek Stone]

I wouldnt consider it good practice at all. One of the key points to look at when you normalize a database is to ensure that data isnt replicated in multiple locations, which is what youd be doing here. I see no reason why your boss cant select the data from the primary table, where it should legitimately reside.

 

[quwiltw]

Why not create a "View" for this and then let your boss SELECT from the view? (or Query if this is Access)