Hi,
I have a problem with designing the logical database model which afterwards
will be use for OLAP.
I have two tables: Patients(patient id(PK), age,....) and
Surgery(patientid(FK),surgeryid(PK),attribute_1(bi t),attribute_2(int),....at
tribute_n(bit)). We have around 200 similar tables as Surgery. In each table
there are between 1000 and 10000 records.
I need following output:
Count of patients having each attribute if it is bit or sum of atributes if
it is INT.

Alexandar Talev
MCDBA,MCT

Not sure if I have this correct but...
You have a single Patient table that holds all patients and you have 200
surgeries ?
Lets take it that there is a Surgery table that you have not shown and
what you are descibing is the realtionship table between the Patient
table and the Surgery table inferring that a patient can go to a number
of surgeries and get an attribute set or a value applied that relates to
that perticular surgery. So the query is saying count(or add up) the
attribute where the patient = xxx
Why an OLAP ? isn't this a simple SQL query summing/counting the
attribute for each patient (and for each surgery if required)? There is
no hierarchy defined and even if there were an hierarchical relationship
grouping Surgeries this could still be done in SQL.
What is the need for OLAP - aggregation, gouping or whatever ? Even if
used there should be no problem in counting a bit or summing and int....



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Clarification:
I have around 200 different tables with around 1000 surgery attributes. I
think I will need OLAP because the users want to find dynamicly (in Excel)
for ex. How many patients are there with for let's say 200 different
attributes which I can choose dynamicly from 1000 available. If I make
report I am losing possibility of dynamic attributes combination which is
easy in OLAP and performance.

AT

"malcolm k" <kraushaarusethisifneeded (AT) anonymousremoveme (DOT) willis.dot.com>
wrote in message news:uf#G0O9lDHA.360 (AT) TK2MSFTNGP12 (DOT) phx.gbl...