designing inheriting entities

Dear All,
our customer has 3 kinds of entites
the first one is the ApplicationCenter where students can register to
exams...
and there are types of app centers like University offices, high schools
etc.. these types goes to another table..
and finally each type has its own instances like University one ,
university2 , univ3 etc. which means there are several more tables Like
universities , highschools , examCenters etc...
the requirement is to have ADD/Edit/Delete screens of all ApplicationCenters
of the customer..
the listing of the centers and their info is straightforward however when it
is time to edit many entities needs to be updated at the same time
.........
i am trying to figure out a table design where i can build sort of
inheriting entities..
any clue?
best regards..
emre dincer
Emre DNER wrote:
> Dear All,
> our customer has 3 kinds of entites
> the first one is the ApplicationCenter where students can register to
> exams...
> and there are types of app centers like University offices, high schools
> etc.. these types goes to another table..
> and finally each type has its own instances like University one ,
> university2 , univ3 etc. which means there are several more tables Like
> universities , highschools , examCenters etc...
> the requirement is to have ADD/Edit/Delete screens of all ApplicationCenters
> of the customer..
> the listing of the centers and their info is straightforward however when it
> is time to edit many entities needs to be updated at the same time
> ........
> i am trying to figure out a table design where i can build sort of
> inheriting entities..
> any clue?
> best regards..
> emre dincer
It is possible to ensure that each common attribute appears only in
one place in the hierarchy for each type of entity. Therefore the
problem of updating the same attribute in multiple places won't arise.
Fifth Normal Form and the Principle of Orthogonal Design are two
principles that will help you achieve a good model. Google for them if
you aren't already familiar with them.
David Portas

designing inheriting entities

Dear All,
our customer has 3 kinds of entites
the first one is the ApplicationCenter where students can register to
exams...
and there are types of app centers like university offices, high schools
etc.. these types goes to another table..
and finally each type has its own instances like university one ,
university2 , univ3 etc. which means there are several more tables Like
universities , highschools , examCenters etc...
the requirement is to have ADD/Edit/Delete screens of all ApplicationCenters
of the customer..
the listing of the centers and their info is straightforward however when it
is time to edit many entities needs to be updated at the same time
........
i am trying to figure out a table design where i can build sort of
inheriting entities..
any clue?
best regards..
emre dincerEmre D=DDN=C7ER wrote:
> Dear All,
> our customer has 3 kinds of entites
> the first one is the ApplicationCenter where students can register to
> exams...
> and there are types of app centers like university offices, high schools
> etc.. these types goes to another table..
> and finally each type has its own instances like university one ,
> university2 , univ3 etc. which means there are several more tables Like
> universities , highschools , examCenters etc...
> the requirement is to have ADD/Edit/Delete screens of all ApplicationCente=[/vbcol
]
rs[vbcol=seagreen]
> of the customer..
> the listing of the centers and their info is straightforward however when =[/vbcol
]
it[vbcol=seagreen]
> is time to edit many entities needs to be updated at the same time
> ........
> i am trying to figure out a table design where i can build sort of
> inheriting entities..
> any clue?
> best regards..
> emre dincer
It is possible to ensure that each common attribute appears only in
one place in the hierarchy for each type of entity. Therefore the
problem of updating the same attribute in multiple places won't arise.
Fifth Normal Form and the Principle of Orthogonal Design are two
principles that will help you achieve a good model. Google for them if
you aren't already familiar with them.
David Portas

designing inheriting entities

Dear All,
our customer has 3 kinds of entites
the first one is the ApplicationCenter where students can register to
exams...
and there are types of app centers like University offices, high schools
etc.. these types goes to another table..
and finally each type has its own instances like University one ,
university2 , univ3 etc. which means there are several more tables Like
universities , highschools , examCenters etc...
the requirement is to have ADD/Edit/Delete screens of all ApplicationCenters
of the customer..
the listing of the centers and their info is straightforward however when it
is time to edit many entities needs to be updated at the same time
........
i am trying to figure out a table design where i can build sort of
inheriting entities..
any clue?
best regards..
emre dincerEmre D=DDN=C7ER wrote:
> Dear All,
> our customer has 3 kinds of entites
> the first one is the ApplicationCenter where students can register to
> exams...
> and there are types of app centers like University offices, high schools
> etc.. these types goes to another table..
> and finally each type has its own instances like University one ,
> university2 , univ3 etc. which means there are several more tables Like
> universities , highschools , examCenters etc...
> the requirement is to have ADD/Edit/Delete screens of all ApplicationCente=rs
> of the customer..
> the listing of the centers and their info is straightforward however when =it
> is time to edit many entities needs to be updated at the same time
> ........
> i am trying to figure out a table design where i can build sort of
> inheriting entities..
> any clue?
> best regards..
> emre dincer
It is possible to ensure that each common attribute appears only in
one place in the hierarchy for each type of entity. Therefore the
problem of updating the same attribute in multiple places won't arise.
Fifth Normal Form and the Principle of Orthogonal Design are two
principles that will help you achieve a good model. Google for them if
you aren't already familiar with them.
--
David Portas

Design Question

Dear All,
I have the following design issue which I am unsure how to solve.
Here's the key information:
I am writing a tool which will send emails/SMS to registered users. The
registered user data will be stored in one database (we'll call it
DB1). No changes can be made to DB1. All information related to the
tool will be stored in a different database (we'll call it DB2). This
will include the following tables (among others):
- "Sent Email" table to store which user (from DB1) received what email
- "User" table to store individuals who have permission to login to the
tool
- "Email Template" table to store email templates
- "Email Template Log" table to record which user created/edited the
template
My specific problem is how to model these relationships in DB2. Will
DB2 contain a "User Look Up" table which stores the ID (PK) of the user
from DB1? Therefore my "Sent Email" table will have a FK from this look
up table? In addition if the scenario was that I needed to record an
attribute "Don't send me messages" would this be stored on the look up
table as well?
Thanks for any help in advance.
Jose"Jose" <discussions@.avandis.co.uk> wrote in message
news:1135436233.215881.325210@.g14g2000cwa.googlegroups.com...
> Dear All,
> I have the following design issue which I am unsure how to solve.
> Here's the key information:
> I am writing a tool which will send emails/SMS to registered users. The
> registered user data will be stored in one database (we'll call it
> DB1). No changes can be made to DB1. All information related to the
> tool will be stored in a different database (we'll call it DB2). This
> will include the following tables (among others):
> - "Sent Email" table to store which user (from DB1) received what email
> - "User" table to store individuals who have permission to login to the
> tool
> - "Email Template" table to store email templates
> - "Email Template Log" table to record which user created/edited the
> template
> My specific problem is how to model these relationships in DB2. Will
> DB2 contain a "User Look Up" table which stores the ID (PK) of the user
> from DB1? Therefore my "Sent Email" table will have a FK from this look
> up table? In addition if the scenario was that I needed to record an
> attribute "Don't send me messages" would this be stored on the look up
> table as well?
> Thanks for any help in advance.
> Jose
>
I guess you'll need a Users table in DB2. What you won't be able to do is
create a foreign key on it that references DB1. Cross-database constraints
aren't supported. You could create a view in DB2 that references the Users
table in DB1.
Have you considered using Notification Services? All you've described and
more ...
http://www.microsoft.com/sql/techno...on/default.mspx
Both 2000 and 2005 editions of NS are available.
David Portas
SQL Server MVP
--

Design of database tables

Dear sir

I have one SQL Server database.
In this database more than 20 tables exists
that their structures is same.
I have two way for design this tables:
1.Create all tables separately(create more than 20 tables)
2.Create one table and separate each group
by type(add column type to table and assign same
value for each group)

What is better solution?
Please help me.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!From the limited information you present I would say 2 is better. Less
maintenance if the table design changes. Easier selection of data if you
need to present data or compare data on multiple groups.

If there was a reason to create 20 identical tables a better solution might
be to create one table and then 20 views, one for each group.

Perhaps this helps.

CJ

"Homauoon Mahboobi" <hmmahboobi@.yahoo.com> wrote in message
news:3f141d62$0$205$75868355@.news.frii.net...
> Dear sir
> I have one SQL Server database.
> In this database more than 20 tables exists
> that their structures is same.
> I have two way for design this tables:
> 1.Create all tables separately(create more than 20 tables)
> 2.Create one table and separate each group
> by type(add column type to table and assign same
> value for each group)
> What is better solution?
> Please help me.
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||>> What is better solution? <<

Only you will know!

A specific logical design is entirely dependant upon a specific business
model. It is the entities, relationships among the entities as well as the
functional dependancies among the attributes which determine the 'right' way
of representing them. Simply grouping & regrouping tables, without
understanding the business predicates makes no sense in logical modelling.

By definition a table should represent one entity type. Thus multiple tables
with 'same' structure seems to be a badly designed schema.

--
- Anith
( Please reply to newsgroups only )|||Homauoon Mahboobi (hmmahboobi@.yahoo.com) writes:
> I have one SQL Server database.
> In this database more than 20 tables exists
> that their structures is same.
> I have two way for design this tables:
> 1.Create all tables separately(create more than 20 tables)
> 2.Create one table and separate each group
> by type(add column type to table and assign same
> value for each group)

2. sounds more appealing, but I have no problem to envision the case where
this would be the wrong way to go. You need to tell more about your data
model, to get some good answer.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Design Help - How to get the Best Design

Dear Experts
Originally in about 1986/87 I was a cobol programmer and was used to doing
things the Master Transaction way. After a long gap i am currently in a
situation of
working with SQL Server 7.0 but somehow i feel my design leans on Master
Transaction Style where i increment the balance in master after every
transaction. MY Question is As Follows:
1. What is the yard stick for a great DB Design.?
2. What kind of Book Should i Read?
3. Any Pointers and Help on Database Design Sample or
courses i can take would be greatly appreciated.
Thanks in Advance and i apologize for this post if it is not in the right
forum.
Manish
Three Cheers to Technet for the Help!
Look at
http://www.databaseanswers.org/data_models/index.htm
for some samples:
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> schrieb im
Newsbeitrag news:27506C1E-A756-4506-AF2D-368E757A82B5@.microsoft.com...
> Dear Experts
> Originally in about 1986/87 I was a cobol programmer and was used to doing
> things the Master Transaction way. After a long gap i am currently in a
> situation of
> working with SQL Server 7.0 but somehow i feel my design leans on Master
> Transaction Style where i increment the balance in master after every
> transaction. MY Question is As Follows:
> 1. What is the yard stick for a great DB Design.?
> 2. What kind of Book Should i Read?
> 3. Any Pointers and Help on Database Design Sample or
> courses i can take would be greatly appreciated.
> Thanks in Advance and i apologize for this post if it is not in the right
> forum.
> Manish
>
> --
> Three Cheers to Technet for the Help!

Design Help - How to get the Best Design

Dear Experts
Originally in about 1986/87 I was a cobol programmer and was used to doing
things the Master Transaction way. After a long gap i am currently in a
situation of
working with SQL Server 7.0 but somehow i feel my design leans on Master
Transaction Style where i increment the balance in master after every
transaction. MY Question is As Follows:
1. What is the yard stick for a great DB Design.?
2. What kind of Book Should i Read?
3. Any Pointers and Help on Database Design Sample or
courses i can take would be greatly appreciated.
Thanks in Advance and i apologize for this post if it is not in the right
forum.
Manish
--
Three Cheers to Technet for the Help!Look at
http://www.databaseanswers.org/data_models/index.htm
for some samples:
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> schrieb im
Newsbeitrag news:27506C1E-A756-4506-AF2D-368E757A82B5@.microsoft.com...
> Dear Experts
> Originally in about 1986/87 I was a cobol programmer and was used to doing
> things the Master Transaction way. After a long gap i am currently in a
> situation of
> working with SQL Server 7.0 but somehow i feel my design leans on Master
> Transaction Style where i increment the balance in master after every
> transaction. MY Question is As Follows:
> 1. What is the yard stick for a great DB Design.?
> 2. What kind of Book Should i Read?
> 3. Any Pointers and Help on Database Design Sample or
> courses i can take would be greatly appreciated.
> Thanks in Advance and i apologize for this post if it is not in the right
> forum.
> Manish
>
> --
> Three Cheers to Technet for the Help!

Design Help - How to get the Best Design

Dear Experts
Originally in about 1986/87 I was a cobol programmer and was used to doing
things the Master Transaction way. After a long gap i am currently in a
situation of
working with SQL Server 7.0 but somehow i feel my design leans on Master
Transaction Style where i increment the balance in master after every
transaction. MY Question is As Follows:
1. What is the yard stick for a great DB Design.?
2. What kind of Book Should i Read?
3. Any Pointers and Help on Database Design Sample or
courses i can take would be greatly appreciated.
Thanks in Advance and i apologize for this post if it is not in the right
forum.
Manish
Three Cheers to technet for the Help!Look at
http://www.databaseanswers.org/data_models/index.htm
for some samples:
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Manish Sawjiani" <ManishSawjiani@.discussions.microsoft.com> schrieb im
Newsbeitrag news:27506C1E-A756-4506-AF2D-368E757A82B5@.microsoft.com...
> Dear Experts
> Originally in about 1986/87 I was a cobol programmer and was used to doing
> things the Master Transaction way. After a long gap i am currently in a
> situation of
> working with SQL Server 7.0 but somehow i feel my design leans on Master
> Transaction Style where i increment the balance in master after every
> transaction. MY Question is As Follows:
> 1. What is the yard stick for a great DB Design.?
> 2. What kind of Book Should i Read?
> 3. Any Pointers and Help on Database Design Sample or
> courses i can take would be greatly appreciated.
> Thanks in Advance and i apologize for this post if it is not in the right
> forum.
> Manish
>
> --
> Three Cheers to technet for the Help!