|
Subject:
|
non-relational database
|
|
Posted By:
|
Michel
|
Post Date:
|
2/20/2006 8:50:30 AM
|
Hello,
I'm involved in the definition of the architecture of a new project.
My customer wants to use a non-relational database. I would like to know if I could use the XML technology for instance, to create my database model? I still collected a lot of articles talking about non-relational projects based on XML.
Do you have a wrox book which covers this topic?
Can I use Sql Server or Oracle as a non-relational container for a such database?
Best Regards
Michel Petrovic
Software research and development Engineer
MCSE 2003
MCSD.NET
|
|
Reply By:
|
David_the_DBA
|
Reply Date:
|
2/20/2006 11:04:49 AM
|
Michel,
That's a pretty broad question. Why does your customer want to use a non-relational database? Why is the customer telling you that instead of giving you higher level requirements and letting you recommend how to do it and where to store the data?
David Lundell
Principal Consultant and Trainer
www.mutuallybeneficial.com
|
|
Reply By:
|
jbenson001
|
Reply Date:
|
2/20/2006 3:52:14 PM
|
Non relational database = VERY BAD!
|
|
Reply By:
|
SQLScott
|
Reply Date:
|
2/20/2006 7:40:08 PM
|
The closest book that would cover this would be Professional XML Databases (yes, a Wrox book). However, like the others, I have to ask, WHY?
Is it doable? Sure. But it will also be slow and cumberson. I would highly recommend you talk your customer out of it. If they want to use XML, they can use the new XML data type that comes with SQL Server 2005. Very fast, powerful, and still allows for "relational xml data".
|
|
Reply By:
|
rstelma
|
Reply Date:
|
2/21/2006 3:05:56 PM
|
Very bad idea. Maybe your customer doesn't know what a relational database is.
Its very easy to do. People do it every day. Just don't create any relationships between your tables. WROX has a very good book, which I own and refer to frequently:
Professional SQL Server 2000 Database Design
Has very good explanations of DB design and normalization which is the theoretical basis for relational database design. Maybe you could dazzle your customer with a few quotes from this book. Ultimately, it will cost everyone more money and usually when you talk of money to customers they are more likely to listen.
Good luck!
|
