Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Who's At Fault


Who's At Fault

Author
Message
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36093 Visits: 18738
Comments posted to this topic are about the item Who's At Fault

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
AndrewJacksonZA
AndrewJacksonZA
SSC-Enthusiastic
SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)SSC-Enthusiastic (179 reputation)

Group: General Forum Members
Points: 179 Visits: 1114
In the meantime, the best defense, as always, is making sure you save often and make backups.

On another disk.

On another continent.
Tom Brown
Tom  Brown
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1342 Visits: 1466
Ten years ago I was team leader in a small software house. When things went wrong there was a bit of a 'blame' culture - and to stop developers squabbling over fault I used to admit responsiblity - especially when the MD (CEO) used to come down looking for a head to put on a pike.
It got to a stage where I'd come accross a group of developers gathered around a PC and say "Its all my fault - what's the problem" - It got a little out of hand, and code comments follows like "Fixed developerX's bad coding". All very well for compiled code - but a customer found some comments in stored procedures and raised a complaint to the MD. We then had a long and protracted exercise in cleaning up all code comments (in both compiled code and SQL) to make sure nothing referred to individuals or customers.

The offending comment. - slightly changed here

-- Fixed xxxx's stupid mistakes. Thats what you get when employing an obvious donkey to do a real developers job.
paul.gregory
paul.gregory
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 95
Losing data? As a developer, I have always taken the approach of delete nothing. Delete is not an SQL command I use. Instead, use an additional column such as 'active'. Then, when the s/&t hits the fan, it's probably a selection issue or some such. Easy to analyse and fix.

And of course, not deleting anything also means I can respond to complaints of the "I didn't do it" sort by looking at the active column of the row and the last user who updated the row, and replying "oh yes you did"

Is it panto season yet?
Someguy
Someguy
SSC-Enthusiastic
SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)SSC-Enthusiastic (157 reputation)

Group: General Forum Members
Points: 157 Visits: 579
All I know is that is wasn't my fault...

:-D

___________________________________________________
“Politicians are like diapers. They both need changing regularly and for the same reason.”
arussell_10
arussell_10
SSC-Enthusiastic
SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)

Group: General Forum Members
Points: 104 Visits: 1321
Weird thought Software companies, how about instead of being first to market, try being the best on the market.... I used to work at a telecom company that was more interested in being first to market with a product instead of being the best on the market. Now, year after year, they are usually in first place on bad customer satisfaction...
bob.willsie
bob.willsie
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
Points: 57 Visits: 151
My second worst frustration in working with an ERP system written in .NET and running on SQL Server is encountering intermittent data loss or corruption.

When you trace through the code, everything looks clean, but somehow out of clean code, and clean input, data was lost or garbage was created.

My absolute worst frustration is that these occurences are considered "acceptable."

Our ERP vendor once supplied a patch and noted that installing it would "make data loss less likely." (actual quote)

So, my question to the group is: What, if any, is an acceptable error rate for data loss or corruption on SQL Server?
GSquared
GSquared
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14375 Visits: 9729
I dislike the whole concept of fault. I prefer responsibility. It's the responsibility of those who can repair the problem. Fault and blame are usually just attempts to dodge responsibility.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
cy-dba
cy-dba
SSC Eights!
SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)SSC Eights! (897 reputation)

Group: General Forum Members
Points: 897 Visits: 963
I sometimes think trying to find out "who" is to blame just adds fuel to the fire. The goal should be to find out "what" is to blame and then fix it. It's been my experience when you point fingers at a specific person, the result is an environment where people are more concerned about covering up mistakes instead of trying to write high quality software.
bmitchell
bmitchell
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2533 Visits: 215
We certainly live in a liability crazy society. There's probably a fortune to be made in writing iron-clad, lawyer-proof disclaimers. A new cottage industry, perhaps... :-)

It seems people are more interested in finding fault than finding solutions. I mean, whose fault is it really if I spill a cup of hot coffee in my lap or I decide to use the blow dryer in the shower?

Responsibility (as mentioned earlier) and accountability are important elements of improving software development.

Along the lines of writing better software, my manager sent out this piece by Charles Fishman yesterday. He notes that errors are ultimately the result of the process.

http://www.fastcompany.com/node/28121/print?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search