View Poll Results: The surest way to database ruin is:

Voters
16. You may not vote on this poll
  • Use of cursors

    0 0%
  • Dynamic SQL

    0 0%
  • Un-normalized design

    5 31.25%
  • All of the above

    4 25.00%
  • Just ask Pat, he'll find it for you!

    7 43.75%
Results 1 to 8 of 8

Thread: Here Brett!

  1. #1
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579

    Here Brett!

    The surest way to database ruin is:

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    What about "Let the users on it"?

  3. #3
    Join Date
    Apr 2002
    Location
    Toronto, Canada
    Posts
    20,002
    you forgot a few other ways to crash and burn....

    - surrogate keys by rote
    - using NOT NULL everywhere
    - executing a query in a loop

    oh, i could go on and on...
    rudy.ca | @rudydotca
    Buy my SitePoint book: Simply SQL

  4. #4
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    I'm a hardcore proponent of surrogate keys, backed up by alternate key definitions for the natural key, but we've been over that bridge before! I think you're willing to allow me to use surrogates, as long as I rigidly enforce the natural key(s) too.

    Misuse of NOT NULL is definitely a path to database disaster, but I don't think I can change the poll once it is started. We'll have to live with the choices that I dreamed up on the spur of the moment, unless somebody wants to start a thread to "build a beter poll" on the road to database ruin... If they do, I'll cheerfully withdraw my poll in favor of a more robust one, with more than 30 seconds of design effort to plan it!

    Inappropriate looping is a means to ruin an application in my opinion. I think that it really can't trash the database, although it can probably emphasize the design errors.

    -PatP

  5. #5
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Jeeze, I fingered that with a poll like this, we'd have the denizons of dbforums gang-piling all over trying to get their votes in on this one. I guess I'll have to scare up some better bait to get people to vote!

    -PatP

  6. #6
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    It's in the wrong forum...
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  7. #7
    Join Date
    Jul 2003
    Location
    The Dark Planet
    Posts
    1,401
    What about ... just ask us ... we will be glad to do it for you
    Get yourself a copy of the The Holy Book

    order has no physical Brett in The meaning of a Kaiser . -database data

  8. #8
    Join Date
    Nov 2003
    Location
    Sussex, England
    Posts
    404

    Best way to ruin a database is

    I used to work with someone who would happily make changes to a working database, and release the new version without testing it with the words, "That should work."

    Often this would be follwed a few days later with, "That should have worked - they're not using it properly".

    Happy days.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •