Design/Modeling books and or advise wanted.

I posted this question long ago to several groups but it didn't generate a
lot of interest so I thought I would try again.
I have been looking for books on database design and or modeling but can't
determine which method or approach would best suite my needs.
I guess this comes from the fact that I'm not sure what the difference is in
the different types of modeling and or design approaches, or for that matter
what possible methods are available. ER, UML ORM....are there others? Are
these different ways to model? Are there other methods? Why should I choose
one over the other?
I mean I'm just the db guy truing to design the best database for our
application. If you can also point out any good books to build up on your
suggestions it would be helpful.
Thanks,
CharlieThere are a couple of suggestions here
http://vyaskn.tripod.com/sqlbooks.htm#rdbms
I personally enjoyed Louis Davidson's "Professionsal SQL Server 2000
Database Design"
Recommendations from "Inside Microsoft SQL Server 2000" by Kalen Delaney:
(from post by B.P.Margolin)
An Introduction to Database Systems, 7th Edition, by C. J. Date
(Addison-Wesley, 1999). A new revision of a classic book, written by a giant
in the field, that covers general relational database concepts. A must-read
for everyone in the database industry.
Database Design for Mere Mortals by Michael J. Hernandez (Addison-Wesley,
1997). A very readable approach to the daunting task of designing a
relational database to solve real-world problems. The book is written in a
database-independent format, so the details can be applied to SQL Server as
well as to other RDMSs you might use.
Handbook of Relational Database Design by Candace C. Fleming and Barbara
Vonhalle (Addison-Wesley, 1988). A fine book that discusses general logical
database design and data modeling approaches and techniques.
SAMS Teach Yourself Microsoft SQL Server 2000 in 21 Days by Richard Waymire
and Rick Sawtell (SAMS Publishing, 2000). A good first book on SQL Server
2000 in tutorial format that gets readers up to speed quickly. One of the
coauthors is a program manager on the SQL Server development team. This
title includes self-test questions for each of the 21 "days."
Database: Principles, Programming, Performance by Patrick O'Neil (Morgan
Kaufmann Publishers, 1994). This thorough textbook provides excellent
introductory materials, so I've placed it high on the list. It also
carefully details a broad spectrum of database topics, including buffer
management and transaction semantics.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Charlie" <cdeaton@.corp.realcomp.com> wrote in message
news:%23$EQz$4hDHA.2296@.TK2MSFTNGP09.phx.gbl...
> I posted this question long ago to several groups but it didn't generate a
> lot of interest so I thought I would try again.
> I have been looking for books on database design and or modeling but can't
> determine which method or approach would best suite my needs.
> I guess this comes from the fact that I'm not sure what the difference is
in
> the different types of modeling and or design approaches, or for that
matter
> what possible methods are available. ER, UML ORM....are there others? Are
> these different ways to model? Are there other methods? Why should I
choose
> one over the other?
> I mean I'm just the db guy truing to design the best database for our
> application. If you can also point out any good books to build up on your
> suggestions it would be helpful.
> Thanks,
> Charlie
>|||Thanks Allen,
Can anyone else comment on approaches to design (ER,UML,ORM').
"Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
news:eDIf6m%23hDHA.2512@.TK2MSFTNGP09.phx.gbl...
> There are a couple of suggestions here
> http://vyaskn.tripod.com/sqlbooks.htm#rdbms
> I personally enjoyed Louis Davidson's "Professionsal SQL Server 2000
> Database Design"
> Recommendations from "Inside Microsoft SQL Server 2000" by Kalen Delaney:
> (from post by B.P.Margolin)
> An Introduction to Database Systems, 7th Edition, by C. J. Date
> (Addison-Wesley, 1999). A new revision of a classic book, written by a
giant
> in the field, that covers general relational database concepts. A
must-read
> for everyone in the database industry.
> Database Design for Mere Mortals by Michael J. Hernandez (Addison-Wesley,
> 1997). A very readable approach to the daunting task of designing a
> relational database to solve real-world problems. The book is written in a
> database-independent format, so the details can be applied to SQL Server
as
> well as to other RDMSs you might use.
> Handbook of Relational Database Design by Candace C. Fleming and Barbara
> Vonhalle (Addison-Wesley, 1988). A fine book that discusses general
logical
> database design and data modeling approaches and techniques.
> SAMS Teach Yourself Microsoft SQL Server 2000 in 21 Days by Richard
Waymire
> and Rick Sawtell (SAMS Publishing, 2000). A good first book on SQL Server
> 2000 in tutorial format that gets readers up to speed quickly. One of the
> coauthors is a program manager on the SQL Server development team. This
> title includes self-test questions for each of the 21 "days."
> Database: Principles, Programming, Performance by Patrick O'Neil (Morgan
> Kaufmann Publishers, 1994). This thorough textbook provides excellent
> introductory materials, so I've placed it high on the list. It also
> carefully details a broad spectrum of database topics, including buffer
> management and transaction semantics.
>
> --
> --
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
> www.SQLDTS.com
> I support PASS - the definitive, global community
> for SQL Server professionals - http://www.sqlpass.org
> "Charlie" <cdeaton@.corp.realcomp.com> wrote in message
> news:%23$EQz$4hDHA.2296@.TK2MSFTNGP09.phx.gbl...
> > I posted this question long ago to several groups but it didn't generate
a
> > lot of interest so I thought I would try again.
> >
> > I have been looking for books on database design and or modeling but
can't
> > determine which method or approach would best suite my needs.
> >
> > I guess this comes from the fact that I'm not sure what the difference
is
> in
> > the different types of modeling and or design approaches, or for that
> matter
> > what possible methods are available. ER, UML ORM....are there others?
Are
> > these different ways to model? Are there other methods? Why should I
> choose
> > one over the other?
> >
> > I mean I'm just the db guy truing to design the best database for our
> > application. If you can also point out any good books to build up on
your
> > suggestions it would be helpful.
> >
> > Thanks,
> > Charlie
> >
> >
>|||UML is for designing software and will produce code that doesn't fit well to
a relational database design. Unfortunately that's just the nature of OOP,
and unless you want to use an object oriented database, you just need to
deal with translating the data into your software.
ER and ORM I consider to be complementary techiques. I prefer designing in
ORM and looking at other people's design as ER diagrams. I find that ORM
gives me more insight into my goals for storing the data, while ER requires
me to focus too much on the actual layout of the data, sometimes losing
sight of the goals for storing it in the first place. Fortunately it's
possible to go back and forth between ER and ORM (at least with Visio, and
if it did a better job of syncing to the database you could even add the
implementation to the mix). I initially learned ORM by going back and forth
between ER and ORM design, until I was comfortable enough with ORM to drop
ER from the initial design process.
I'd also just like to mention that "Handbook of Relational Database" was the
very first book I ever read on database design (that was when I showed up on
my first day of my university work term with no database experience -- not
even DB-III -- to find a FoxPro box on my desk and a request to "build us an
inventory management system"). I still consider it the most useful book I've
ever read on relational databases.
Colin
"Charles Deaton" <mssql@.mssql.com> wrote in message
news:%23PyUhsBiDHA.2296@.TK2MSFTNGP09.phx.gbl...
> Thanks Allen,
> Can anyone else comment on approaches to design (ER,UML,ORM').
> "Allan Mitchell" <allan@.no-spam.sqldts.com> wrote in message
> news:eDIf6m%23hDHA.2512@.TK2MSFTNGP09.phx.gbl...
> > There are a couple of suggestions here
> >
> > http://vyaskn.tripod.com/sqlbooks.htm#rdbms
> >
> > I personally enjoyed Louis Davidson's "Professionsal SQL Server 2000
> > Database Design"
> >
> > Recommendations from "Inside Microsoft SQL Server 2000" by Kalen
Delaney:
> > (from post by B.P.Margolin)
> >
> > An Introduction to Database Systems, 7th Edition, by C. J. Date
> > (Addison-Wesley, 1999). A new revision of a classic book, written by a
> giant
> > in the field, that covers general relational database concepts. A
> must-read
> > for everyone in the database industry.
> >
> > Database Design for Mere Mortals by Michael J. Hernandez
(Addison-Wesley,
> > 1997). A very readable approach to the daunting task of designing a
> > relational database to solve real-world problems. The book is written in
a
> > database-independent format, so the details can be applied to SQL Server
> as
> > well as to other RDMSs you might use.
> >
> > Handbook of Relational Database Design by Candace C. Fleming and Barbara
> > Vonhalle (Addison-Wesley, 1988). A fine book that discusses general
> logical
> > database design and data modeling approaches and techniques.
> >
> > SAMS Teach Yourself Microsoft SQL Server 2000 in 21 Days by Richard
> Waymire
> > and Rick Sawtell (SAMS Publishing, 2000). A good first book on SQL
Server
> > 2000 in tutorial format that gets readers up to speed quickly. One of
the
> > coauthors is a program manager on the SQL Server development team. This
> > title includes self-test questions for each of the 21 "days."
> >
> > Database: Principles, Programming, Performance by Patrick O'Neil (Morgan
> > Kaufmann Publishers, 1994). This thorough textbook provides excellent
> > introductory materials, so I've placed it high on the list. It also
> > carefully details a broad spectrum of database topics, including buffer
> > management and transaction semantics.
> >
> >
> > --
> > --
> >
> > Allan Mitchell (Microsoft SQL Server MVP)
> > MCSE,MCDBA
> > www.SQLDTS.com
> > I support PASS - the definitive, global community
> > for SQL Server professionals - http://www.sqlpass.org
> >
> > "Charlie" <cdeaton@.corp.realcomp.com> wrote in message
> > news:%23$EQz$4hDHA.2296@.TK2MSFTNGP09.phx.gbl...
> > > I posted this question long ago to several groups but it didn't
generate
> a
> > > lot of interest so I thought I would try again.
> > >
> > > I have been looking for books on database design and or modeling but
> can't
> > > determine which method or approach would best suite my needs.
> > >
> > > I guess this comes from the fact that I'm not sure what the difference
> is
> > in
> > > the different types of modeling and or design approaches, or for that
> > matter
> > > what possible methods are available. ER, UML ORM....are there others?
> Are
> > > these different ways to model? Are there other methods? Why should I
> > choose
> > > one over the other?
> > >
> > > I mean I'm just the db guy truing to design the best database for our
> > > application. If you can also point out any good books to build up on
> your
> > > suggestions it would be helpful.
> > >
> > > Thanks,
> > > Charlie
> > >
> > >
> >
> >
>|||You might as well have posted a message asking what is the best
religion ;-)
Your questions are so broad, that there's no way to answer
themsuccinctly. So I'm not surprised your previous posting along the
same lines generated little interest.
I'd do a groups.googlecom search and look for discussions on the
topics that interest you so that you can garner a wide range of
previously-expressed opinions. Amazon.com is a good place to search
for books since they post reviews.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Tue, 30 Sep 2003 16:17:56 -0400, "Charlie"
<cdeaton@.corp.realcomp.com> wrote:
>I posted this question long ago to several groups but it didn't generate a
>lot of interest so I thought I would try again.
>I have been looking for books on database design and or modeling but can't
>determine which method or approach would best suite my needs.
>I guess this comes from the fact that I'm not sure what the difference is in
>the different types of modeling and or design approaches, or for that matter
>what possible methods are available. ER, UML ORM....are there others? Are
>these different ways to model? Are there other methods? Why should I choose
>one over the other?
>I mean I'm just the db guy truing to design the best database for our
>application. If you can also point out any good books to build up on your
>suggestions it would be helpful.
>Thanks,
>Charlie
>