SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Visual Studio Database Tools


Visual Studio Database Tools

Author
Message
SanDroid
SanDroid
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1588 Visits: 1046
Tom.Thomson (3/17/2011)
Actually, in the context of a RDBMS, it sounds appallingly uncool - back to the bad old days of the network or heriarchical database models (which would have been a sensible approach to handling XML in an RDBMS, but someone had to reinvent the wheel, didn't they, and forgot it should have no sharp corners) or, even worse, forward to the long promised but never yet delivered working nontrivial OODBMS.


Tom,
I ask this question to anyone that talks about OODBMS vs RDBMS.

Define the differance in schema of a database on a OODBMS from that of a RDBMS database that is fully ACID and Normalized.

BTW: Please re-read the lastest information on Database Normalization and the 5th Normal Form before answering.
:SMOOTH:
Jamie Thomson
Jamie Thomson
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1279 Visits: 188
SanDroid (3/18/2011)
Tom.Thomson (3/17/2011)
Actually, in the context of a RDBMS, it sounds appallingly uncool - back to the bad old days of the network or heriarchical database models (which would have been a sensible approach to handling XML in an RDBMS, but someone had to reinvent the wheel, didn't they, and forgot it should have no sharp corners) or, even worse, forward to the long promised but never yet delivered working nontrivial OODBMS.


Tom,
I ask this question to anyone that talks about OODBMS vs RDBMS.

Define the differance in schema of a database on a OODBMS from that of a RDBMS database that is fully ACID and Normalized.

BTW: Please re-read the lastest information on Database Normalization and the 5th Normal Form before answering.
:SMOOTH:


Let's not fight. this is neither the time nor the place :-)

Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson
SanDroid
SanDroid
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1588 Visits: 1046
Jamie Thomson (3/18/2011)
SanDroid (3/18/2011)
Tom.Thomson (3/17/2011)
Actually, in the context of a RDBMS, it sounds appallingly uncool - back to the bad old days of the network or heriarchical database models (which would have been a sensible approach to handling XML in an RDBMS, but someone had to reinvent the wheel, didn't they, and forgot it should have no sharp corners) or, even worse, forward to the long promised but never yet delivered working nontrivial OODBMS.


Tom,
I ask this question to anyone that talks about OODBMS vs RDBMS.

Define the differance in schema of a database on a OODBMS from that of a RDBMS database that is fully ACID and Normalized.

BTW: Please re-read the lastest information on Database Normalization and the 5th Normal Form before answering.
:SMOOTH:

Let's not fight. this is neither the time nor the place :-)


Who is fighting? <looking around> I honestly would like an answer to my question and I respect Tom's opinion.

I have heard a lot of talk about OODBMS, but only that.
I have never heard an anwer to that question that mentioned something we can not do with MS SQL Server.

Perhaps the real answer is "A OODBMS system would not allow the creation of DB schema that is un-normalized and non ACID Compliant."
Tom Thomson
Tom Thomson
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14582 Visits: 12238
SanDroid (3/18/2011)
Jamie Thomson (3/18/2011)
SanDroid (3/18/2011)
Tom.Thomson (3/17/2011)
Actually, in the context of a RDBMS, it sounds appallingly uncool - back to the bad old days of the network or heriarchical database models (which would have been a sensible approach to handling XML in an RDBMS, but someone had to reinvent the wheel, didn't they, and forgot it should have no sharp corners) or, even worse, forward to the long promised but never yet delivered working nontrivial OODBMS.


Tom,
I ask this question to anyone that talks about OODBMS vs RDBMS.

Define the differance in schema of a database on a OODBMS from that of a RDBMS database that is fully ACID and Normalized.

BTW: Please re-read the lastest information on Database Normalization and the 5th Normal Form before answering.
:SMOOTH:

Let's not fight. this is neither the time nor the place :-)


Who is fighting? <looking around> I honestly would like an answer to my question and I respect Tom's opinion.

I have heard a lot of talk about OODBMS, but only that.
I have never heard an anwer to that question that mentioned something we can not do with MS SQL Server.

Perhaps the real answer is "A OODBMS system would not allow the creation of DB schema that is un-normalized and non ACID Compliant."

I didn't for a mement think you intended to start a fight. I suspect Jamie thought that because he has seen fights between "relational" people and "oo people" before. But his point that this is neither the time nor the place applies equally to the debate about how OODBMS differs from RDBMS, or to the debate about what an OODBMS should or shouldn't be, as to a fight - this thread is for discussing the question and answer about VS that Jamie supplied, not for drifting off into distant theoretical realms. If we want to have tthe OODBMS discussion (and it might be a useful one to have) we should start a thread specifically (if one doesn't already exist - it may do) for it rather than hijacking Jamie's thread for it. I'll give you a short answer here, because it's easy: since there is no broad agreement amongst OO people interested in databases (nor indeed amongst database people interested in OO) as to what an OODBMS should be (or would be, or could be, or is - people don't even agree on which of these verb forms is appropriate here) the only sensible answer to your question is "I don't know" (but I would also say that it's pretty unclear how or even whether normalisation would apply to an OODBMS). The discussion can be continued elsewhere, if you wish.

Tom

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search