Reputation
1,468
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
5 9
Newest
 Yearling
Impact
~71k people reached

11h
comment Why would I need a third table in a one-to-many relationship?
Good point. The third table makes it possible to represent an optional relationship without introducing NULLS.
Jul
29
answered Why would I need a third table in a one-to-many relationship?
Jul
29
comment Why would I need a third table in a one-to-many relationship?
Either you misinterpreted what your professor said, or your professor misinformed you.
Jul
28
comment Why is Database Administration so hard?
I was a database consultant for a few years. The sick puppies I had to nurse back to health included not only corrupted databases but seriously damaged DBAs. An undergraduate major in psychology would have been helpful.
Jul
26
answered Database design appoach confirmation
Jul
25
comment Database design appoach confirmation
I think you are mixed up about parent and child. The existing structure you describe, with claim containing loanId, establishes a many to one relationship between claims and loans. Why do you say that in the legcy system the claim is taken as parent?
Jul
16
comment MySQL Db design: Optional data in separate table or as NULL values in original table
It depends on what you are going to do with the data. Without this information, we are just guessing about performance.
Jul
12
comment How to relate a table to other two?
Is there a name for some superclass that includes both venues and products as subclasses? There is a tag called subtypes that group together questions of that ilk.
Jul
10
revised Row for each date, or 31 columns?
added edit based on comments
Jul
10
comment Row for each date, or 31 columns?
There is a side point in the previous comment. "I once had to deal with". This illustrates a common (although not universal) feature of captured data. It tends to outlive it's expected lifespan, and is subjected to mission creep, usually by a hapless successor.
Jul
9
comment Row for each date, or 31 columns?
I'm going to leave adding more detail to others. What I will tell you is that what you are engaged in is data architecture, regardless of whether you are only a code monkey or not.
Jul
9
comment Row for each date, or 31 columns?
If you want to understand crosstabulation, you can start here, en.wiktionary.org/wiki/cross_tabulation and then follow the links.
Jul
9
comment Row for each date, or 31 columns?
The transition from code monkey to data architect is a rough one. I know, because I made that transition, many years ago. Data that is thrown together by code monkeys nearly always comes back to haunt people who come along later.
Jul
9
answered Row for each date, or 31 columns?
Jul
6
answered Are junction tables a good practice?
Jul
6
comment Are junction tables a good practice?
I think you are misusing the term "Left Join". This has a very specific meaning when SQL is being discussed, and Left Join is completely extraneous to the problem as you have presented it. If this is part of a larger problem, and the larger problem requires a left join, then please rephrase your question so we can understand the larger problem.
Jul
6
answered Help with a scenario of music groups and members in ERD design
Jul
3
comment Database design, many rows or many columns?
The question is really about table composition, or rather, table decomposition. The subject of table decomposition usually comes up in discussions about normalization. Is your question really about whether normalizing speeds up or slows down database operations?
Jul
1
comment Conceptual ERD Multi-table many to many, or possibly recursive?
@MVCNewbie you can mark this answer as correct by clicking the check box on the left, if you choose to. This will help future visitors, and also add to MDCCL's reputation.
Jun
29
comment Conceptual ERD Multi-table many to many, or possibly recursive?
AFAICT, the table Profile_Members represents a recursive many-to-many relationship between one Profile and Another. That's as far as I've gotten.