Human error. Human malice. The vulnerabilities are the same. A sensible risk management strategem has always been not to place all of one's eggs in one basket,...

I think the answer "it depends" is inescapable but begs the question of how much downtime you can you afford (lost production, lost sales, customer inconvenience) versus the use of...

David Ziffer (10/14/2010)

---

... American industry is losing vast sums of money due to the poor design, inefficiency and high error rate of the software that it pays people to develop....

A very interesting article. I have used variants of some of these suggestions and ideas in my own designs, plus a few of my own invention with extremely good...

I didn't know this but nor do I have the...

I couldn't agree more and hence the danger to users...

skamath wrote:

So, would you agree that if you encounter *exactly* such instances (and you seem to indicate that you do), that unless you have a time machine to travel back...

The code in the article works, but is it enough to leave it at that? If you are stuck with a production database that allows duplicates in tables, you...

From some of the replies to my post, I'm seeing that old schism of "code guru" and "design guru" is alive and well. I have never denied duplicates are...

thisisfutile (9/22/2010)

---

@trubolotta Not trying to start an argument here, but hindsight is 20/20 for everyone. Sometimes we find ourselves in a situation like the OP is describing (or...

This appears to be one of those articles that creates a problem based on poor design and purports to correct it using some bloated functionality of SQL Server. If...

On the issue of undergraduate course for database development I have some mixed concerns.

I recall an incident where a developer asked for advice on the design of a table. ...

While I find the discussion of how to best use the getdate() function interesting, I also find it distressing that the pursuit of code efficiency brushes aside the more important...

I don't want to hit this too hard but I see the example more as a case for improved design versus dernomarlization. Just a few obervations if I may:

1)...

Well said and to add to the name menagerie, I have always called them Join Tables since they join one entity to another.

For those who think this is "bad design",...