Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
No More SOX
25 posts, Page 1 of 3
1
2
3
»
»»
No More SOX
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Saturday, May 30, 2009 10:25 PM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 6:14 PM
Points: 31,421,
Visits: 13,734
Comments posted to this topic are about the item
No More SOX
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #726282
Jeff Moden
Jeff Moden
Posted Sunday, May 31, 2009 11:36 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Yesterday @ 9:57 PM
Points: 32,906,
Visits: 26,790
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.
Truly Yours,
BSOFH on SOX steroids
p.s. That goes for your bloody undocumented, just-as-performance-challenged GUI code, too!
--Jeff Moden
"
RBAR
is pronounced "ree-bar" and is a "Modenism" for "
R
ow-
B
y-
A
gonizing-
R
ow".
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."
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Post #726417
Jeff Moden
Jeff Moden
Posted Sunday, May 31, 2009 11:52 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Yesterday @ 9:57 PM
Points: 32,906,
Visits: 26,790
Heh... sorry... I'm holding back... I should tell you how I really feel.
--Jeff Moden
"
RBAR
is pronounced "ree-bar" and is a "Modenism" for "
R
ow-
B
y-
A
gonizing-
R
ow".
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."
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Post #726423
Tom Fischer
Tom Fischer
Posted Monday, June 01, 2009 6:15 AM
SSC Rookie
Group: General Forum Members
Last Login: Friday, November 09, 2012 12:30 PM
Points: 27,
Visits: 60
Have to (strongly) agree with the ambiguous Mr. Moden.
One of the downsides of SOX that I’ve witnessed has been its casual interpretation to justify requests. For example, one manager used SOX to justify hiring another DBA. Another involved requesting hardware upgrades.
Post #726570
Mike Hinds
Mike Hinds
Posted Monday, June 01, 2009 6:32 AM
Mr or Mrs. 500
Group: General Forum Members
Last Login: 2 days ago @ 8:35 AM
Points: 527,
Visits: 770
SOX gave us a start to prepare for what was to come. As mentioned by all above, we now have the law on our side when we ask for controls, and the time and materials to implement them.
The regional bank I work for was hit by eastern European hackers a year ago. SOX helped in two ways:
1) We were partially prepared for the intrusion, and as such the actual damage to customer data was limited. Law enforcement gave us a huge P/R boost in assuring our customers that we had been well prepared.
2) Many staff were prepared to respond quickly and appropriately, by having done many of the steps in lesser intensity over the last five years.
Regards, Mike
Post #726590
Andrew Peterson-472853
Andrew Peterson-472853
Posted Monday, June 01, 2009 7:02 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, January 16, 2013 7:40 AM
Points: 136,
Visits: 259
We do need SOX, but corporate executives hate it.
It limits their ability to softly manage their short term reported financials, and makes them responsible. In one of my past careers (I am a CPA) I audited the financials of many companies. If you remember the collapse of Enron and Arthur Andersen, I can tell you from firsthand knowledge that it was only a matter of time before a major accounting firm imploded.
The more you are prepared, the less you need it.
Post #726617
Someguy
Someguy
Posted Monday, June 01, 2009 7:06 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Monday, May 07, 2012 10:39 AM
Points: 153,
Visits: 565
This was an interesting editorial for me because prior to this I had only heard Sarbanne-Oxley critisized for the "Mark to Market" provisions. See link below as an example:
http://www.forbes.com/2008/09/29/mark-to-market-oped-cx_ng_0929gingrich.html
Apparently SOX is more complex than this single issue. Thanks for the enlightenment.
I haven't had time to read the whole act (and I don't feel too guilty about that - it seems most of Congress doesn't have time to read their own legislation nowadays). Might it be that it is a series of provisions that need to be considered individually? Perhaps those of you who have implemented applications in response to the act could further enlighten us...
___________________________________________________
“Politicians are like diapers. They both need changing regularly and for the same reason.”
Post #726621
Hugo Shebbeare
Hugo Shebbeare
Posted Monday, June 01, 2009 7:24 AM
Grasshopper
Group: General Forum Members
Last Login: Wednesday, May 01, 2013 3:03 PM
Points: 11,
Visits: 224
Glad to see from above the support for Internal Controls, certainly makes not only the DBAs life easier, but also, more importantly, the strength of an organisation's systems' integrity.
I went into detail on this already here, with an anecdote or two:
http://www.sqlservercentral.com/blogs/hugo/archive/2009/02/15/the-importance-of-the-segregation-of-duties-with-respect-to-internal-controls.aspx
Here in Canada, we have (aka C-SOX) Bill C-158 - unfortunately, most developers here have to be convinced that
this is the law
and not just 'overhead' to make their lives difficult.
Town of Mount Royal, QC
514 812 5087 (txt also)
hugo@intellabase.com (msn im also)
Post #726639
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Monday, June 01, 2009 7:36 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 6:14 PM
Points: 31,421,
Visits: 13,734
Very interesting. I was expecting to see more complaints about SOX, but maybe I'm not out of touch as a DBA. This law definitely helps DBAS, or anyone that wants to better manage and control their environment, without such a fly-by-the-seat-of-my-pants attitude that used to predominate.
I guess the DBAs don't want this repealed.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #726648
KWymore
KWymore
Posted Monday, June 01, 2009 7:37 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 8:52 AM
Points: 2,574,
Visits: 1,532
At my old company, data was managed very haphazardly and pretty much anyone could get access to systems internally if they asked the right people. SOX made us tighten down our systems, document our systems and actually come up with back up strategies which were barely there before. It actually required admins and dba's to learn the systems that they were working with better and in turn exposed a number of large potential issues that we might not have found before. After the first 2 years of SOX audits, it just became another yearly ritual for us, same as year end reporting and routine maintenance. One can imagine how many public companies might have fudged the numbers in today's economy if SOX wasn't a concern.
Post #726649
« Prev Topic
|
Next Topic »
25 posts, Page 1 of 3
1
2
3
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.