Microsoft
Software
Hardware
Network
Question : Why should 1:1 Relationships be used for Entities with Subsclasses?
Why should attributes that are specific to distinct subsets of an entity be separated out into separate tables with 1:1 links to the main entity table?
For example, a superstore that sells everything from soup to lawnmower nuts, has a main Products table (atributes: Brand, UPC) and separate tables for sporting goods products (attributes: Sport, Season) and food products (attributes: ShelfLife, DiabeticFriendly). This may appeal to one's sense of data organization, but creates some overhead (must manage multiple tables) and some restrictions (there is no way to implement bilateral RI in MS Access). Are there any other pros and cons? Assume that ULS is not used or required.
I've googled some links in favour:
•
http://onlamp.com/pub/a/on
lamp/2001/
03/20/abou
tSQL.html
•
http://msdn.microsoft.com/
en-us/libr
ary/dd3267
69(VS.85).
aspx
and others against:
•
http://www.sum-it.nl/cursu
s/dbdesign
/english/i
ntro030.ph
p3
•
http://msdn.microsoft.com/
en-us/libr
ary/4s9x13
w7.aspx
•
http://www.docstoc.com/doc
s/4193380/
Relational
-Database-
Relationsh
ip-Types
Answer : Why should 1:1 Relationships be used for Entities with Subsclasses?
This has the steps if your using sql server 2008...
http://www.mssqltips.com/t
ip.asp?tip
=1709
Random Solutions
When I un-install GroupWise 6.5, Microsft Excel will not open (compliation errors).
Formatting a Hard Drive with sensitive data
PHP sql statements
Laptop action keys not functioning on debian
Adding Exchange to an existing POP in Outlook
USB port on compaq laptop w/XP will not work with USB mouse
Network Segments
Outlook Anywhere
using autoexec macro to update database with windows scheduled tasks
Dinkum template library "map" syntax