Re: Database market share 2004
DA Morgan <damorgan@psoug.org> wrote: >> Oh, the data is valuable alright and in use by Blue Chip companies >> across the world, many of whom would be clients of a certain large >> aerospace manufacturing company situated in Washington State that you >> can't talk about - United Airlines is an example of such client. >> It could well be that the UA dba's are tearing their hair out, but >> they're probably not the ones who made the purchasing decision about >> the s/ware, and rocking the boat mightn't do their careers any good. >No but on purely theoretical grounds, because I know we are NOT talking >about United Airlines, they MUST be compliant with Sarbanes-Oxley. >Compliance is not optional ... it is mandatory. Maybe they are compliant? Why does using a db as a bitbucket make you uncompliant? (DRI is enforced in the creation scripts). Maybe you could point me to a site that gives an overview of Sarbanes-Oxley for the non-specialist accountant (obviously I can Google, but you might have a good one handy?). I know for a fact that this company has UA as a client, but there may be wheels within wheels - web interfaces that connect to systems (which may be outside the US or may not be) and which take data from them (possibly old mainframe TPF type systems) which are possibly compliant? I'm not exactly sure where the buck stops and I would imagine that there would be lots of fingerpointing if anyone was looking at any time in the slammer. Suits and countersuits... maybe I should have done law? >So refer to the simulated conversation above. Management can not and >will not break federal law to save a few dollars. It just isn't going >to happen. Not after Enron. Not after WorldCom. Not after .... As I said, I'm not privy to the higher echelons of the arrangements these companies have made with each other - if you're interested I could give you a brief outline offline... Paul... -- plinehan __at__ yahoo __dot__ __com__ XP Pro, SP 2, Oracle, 9.2.0.1.0 (Enterprise Ed.) Interbase 6.0.2.0; When asking database related questions, please give other posters some clues, like operating system, version of db being used and DDL. The exact text and/or number of error messages is useful (!= "it didn't work!"). Thanks. Furthermore, As a courtesy to those who spend time analysing and attempting to help, please do not top post.
Paul wrote: > Maybe they are compliant? Why does using a db as a bitbucket make you > uncompliant? (DRI is enforced in the creation scripts). Maybe you > could point me to a site that gives an overview of Sarbanes-Oxley for > the non-specialist accountant (obviously I can Google, but you might > have a good one handy?). I assume they are. The point is auditability. The ability to identify everyone that has touched the data, how they touched it, why they touched it, and the source of the transation. And done in a way that can not be circumvented. And that is the key. Any system that allows a DBA to log in and insert, update, or delete and not be logged is a potential legal issue. >>So refer to the simulated conversation above. Management can not and >>will not break federal law to save a few dollars. It just isn't going >>to happen. Not after Enron. Not after WorldCom. Not after .... > > As I said, I'm not privy to the higher echelons of the arrangements > these companies have made with each other - if you're interested I > could give you a brief outline offline... > > Paul... Not necessary but I never lack for interest if you are so inclined. Regards, -- Daniel A. Morgan http://www.psoug.org damorgan@x.washington.edu (replace x with u to respond)