|
|
Posted by Tibor Karaszi on 05/04/06 16:58
That sounds weird. IF the formatted data is stored for performance reasons, I'd at least have it in
another database. But I prefer to do the report off of the production database (if low activity and
doesn't have perf impact), or have a different database better suited for reporting off of.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rlm" <groups@rlmoore.net> wrote in message
news:1146747407.524001.97330@j33g2000cwa.googlegroups.com...
> The IT group that I work with has the habit of gathering data,
> formatting (i.e. in reports) and then storing the same formated data in
> the same database.
>
> I think the practice is wrong. I think the activity is fundamentally
> wrong because we are storing the exact same data in a database in two
> different locations. Somehow I have the impression that database design
> is about "oneness".
>
> I believe that collecting the data and then storing summerized data for
> reporting into a data warehouse would be the right solution.
>
> I am getting flack for my viewpoint.
>
> Am I all washed up?
>
Navigation:
[Reply to this message]
|