> > >> I am about to start designing schema for a large database. I am
> > trying to weigh up the pros and cons for using either a GUID or auto
> > incrementing IDENTITY column for the primary keys. <<
> > This is obviously your first large database project, and you have never
> > had course in data modeling. You have set up a False Dichotomy. A very
> > false one, in fact.
> > Neither a GUID or IDENTITY can be a key **by definition**; they are
> > attributes of the PHYSICAL storage and have nothing to do with the
> > logical model. You are starting on the physical implementation without
> > a logical model. And you're already trapping yourself in one of two bad
> > decisions that will destroy the dat integrity of the project.
> > The right questions to ask at the start of a project are:
> > 1) Can I buy a package? How much does it cost?
> > 2) Has anyone done this before? Who?
> > 3) What are the industry standards for this application?
> > 4) What are the entities?
> > 5) What are the relationships?
> > 6) What are the business rules?
> > Have you learned ORM yet? Might be the best place to start.
> > I made a living fixing database projects that get ed up by things
> > like this. I usually come in after the first year. That is a "magic
> > number" because it is just enough time fot the database to get large,
> > have been used enough to be important and to have someone do an annual
> > report off of it. That is when the owners see that everything is crap
> > and that they need to clean it up.
> > --CELKO--
> > ===========================
> > Please post DDL, so that people do not have to guess what the keys,
> > constraints, Declarative Referential Integrity, datatypes, etc. in your
> > schema are.
> > *** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
> > Don't just participate in USENET...get rewarded for it!