THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is AndyLeonard.blog.

The Perfect Trap

This blog has moved! You can find this content at the following new location:

http://andyleonard.blog/2012/03/05/the-perfect-trap/

Published Monday, March 5, 2012 8:00 AM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

K. Brian Kelley said:

Welcome to the light, my friend. ;-)

March 5, 2012 1:31 PM
 

Mike Adkins said:

Working for a "little" company in Jacksonville where I ran into you the first time, I admit this post irked me a bit; but only because it's mostly true.  As a developer in an aggressive culture, I am constantly asked, hounded, beat with wet noodles, etc., as management constantly wants this-or-that change yesterday.  If I don't get it done right away I don't get a raise.  Meanwhile, I beg, plead, and bribe the DBAs to get something done, and I have to spend an hour in a meeting that they call where they explain why it can't or shouldn't be done.  And then the devs take the heat for not getting it done.  So I concur: "how hard can it be to tell developers 'No'?"

Pardon the rant.  I'm done...

March 6, 2012 2:02 PM
 

RichB said:

@Mike...

Would you be the one spending the rest of the night and the next day fixing up the database after some kneejerk developer implemented something a little... incomplete?

Would you be the one who had to tell the CEO that you've lost 12 hours of customer data because a change went through that effectively serialised all the connections into a single open transaction that someone then rolled back.

Oh, and no he can't have his database back because the rollback will take another 10 hours or so, resulting in at least 24 hours effective downtime for a sloppy piece of error handling on a slightly weak piece of database design that just had to be done in a hurry?

If so, go ahead.  Make the change.

<_<

March 7, 2012 6:32 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

News

My Latest Book:

Community Awards



Friend of Red Gate

Contact Me

Archives

Privacy Statement