Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
UNION Help
12 posts, Page 2 of 2
««
1
2
UNION Help
Rate Topic
Display Mode
Topic Options
Author
Message
Eugene Elutin
Eugene Elutin
Posted Tuesday, September 11, 2012 7:55 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 9:40 AM
Points: 2,596,
Visits: 4,507
CELKO (9/11/2012)
I have a database that contains a number of individual tables for each sales agents.
This design flaw is called attribute splitting. Would you have “Male_Personnel” and “Female_Personnel” tables or a single “Personnel” table? Pretty obvious, isn't it? ...
That is really bright idea! Actually, taking in count progress of the west civilization in whole, you need at least three tables:
“Male_Personnel”, “Female_Personnel” and "Unknown_Personnel"
Actually the attribute splitting may not be a flaw, but done on purpose. One of the common places where you can see this kind of picture is data warehouses (non-conformed dimensions).
There are other design patterns where attribute splitting is a feature - not a flow.
_____________________________________________
"The only true wisdom is in knowing you know nothing"
"O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!"
(So many miracle inventions provided by MS to us...)
How to post your question to get the best and quick help
Post #1357428
Brandie Tarvin
Brandie Tarvin
Posted Tuesday, September 11, 2012 8:09 AM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 9:57 AM
Points: 6,724,
Visits: 5,796
Eugene Elutin (9/11/2012)
Actually the attribute splitting may not be a flaw, but done on purpose. One of the common places where you can see this kind of picture is data warehouses (non-conformed dimensions).
Or companies that vend solutions to multiple customers and can't mix their data for legal reasons. Like health insurance software companies that host the data on site. I actually worked for one of those.
Of course, in that instance, any request to mingle the data via UNION (at least in the U.S.) would be a Bad Idea.
Brandie Tarvin, MCITP Database Administrator, MCDBA, MCSA
Webpage
:
http://www.BrandieTarvin.net
LiveJournal Blog
:
http://brandietarvin.livejournal.com/
On
LinkedIn!
,
Google+
, and
Twitter
.
Freelance Writer:
Shadowrun
Latchkeys: Nevermore
,
Latchkeys: The Bootleg War
, and
Latchkeys: Roscoes in the Night
are now available on Nook and Kindle.
Post #1357444
« Prev Topic
|
Next Topic »
12 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.