From: "Frugal Sam" <frugalsam@hotmail.com>
Newsgroups: comp.databases.theory
References: <d272bee7.0105231000.48bf2ea3@posting.google.com>
Subject: Re: Designing a Reporting Database
Lines: 12
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Message-ID: <lhXY6.6017$3d3.456284@bgtnsc05-news.ops.worldnet.att.net>
Date: Sat, 23 Jun 2001 07:10:09 GMT
NNTP-Posting-Host: 12.72.57.80
X-Complaints-To: abuse@worldnet.att.net
X-Trace: bgtnsc05-news.ops.worldnet.att.net 993280209 12.72.57.80 (Sat, 23 Jun 2001 07:10:09 GMT)
NNTP-Posting-Date: Sat, 23 Jun 2001 07:10:09 GMT
Organization: AT&T Worldnet


I am currently working on a similar project. Of course, I have much fewer
than 100 tables to work with.

The first thing I would suggest you do, before focusing on the design of
your reporting database, is to analyze the reporting requirements of your
users.
As you learn more and more about how your users plan to query this data, the
database design might well become almost trivial.

All the best.