SOX actually made my life a little easier. I no longer have to argue with a bunch of people about locking down the Production Servers. I no longer have to listen to interminable dribble and explain over and over about why I don't believe Developers should have anything other than Read Only access to the Production Servers, if that.
Now, I have a "3" word reason that they can't argue with. "It's the Law". Period. End of Story. Next problem please. And, oh yes, take your whiney hiney and your boss' gotta-have-it-now-'cause-I-dunno-how-to-write-a-schedule PITA attitude down the hall and put your cruddy, performance challenged, inaccurate, untested, POS code through a code review and some decent Unit and UAT Testing before you give it to me for promotion to Production. Make sure you have a backout plan, too, sonny. :-P
BSOFH on SOX steroids
p.s. That goes for your bloody undocumented, just-as-performance-challenged GUI code, too! :-D
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs