Return-Path: Received: from ensim.rackshack.net (root@localhost) by orafaq.net (8.11.6/8.11.6) with ESMTP id gBB3sE115114 for ; Tue, 10 Dec 2002 21:54:15 -0600 X-ClientAddr: 209.68.248.164 Received: from newsfeed.cts.com (newsfeed.cts.com [209.68.248.164]) by ensim.rackshack.net (8.11.6/8.11.6) with ESMTP id gBB3sC315108 for ; Tue, 10 Dec 2002 21:54:12 -0600 Received: from fatcity.UUCP (uucp@localhost) by newsfeed.cts.com (8.9.3/8.9.3) with UUCP id QAA45631; Tue, 10 Dec 2002 16:31:39 -0800 (PST) Received: by fatcity.com (26-Feb-2001/v1.0g-b72/bab) via UUCP id 00517075; Tue, 10 Dec 2002 14:54:17 -0800 Message-ID: Date: Tue, 10 Dec 2002 14:54:17 -0800 To: Multiple recipients of list ORACLE-L X-Comment: Oracle RDBMS Community Forum X-Sender: "Orr, Steve" Sender: root@fatcity.com Reply-To: ORACLE-L@fatcity.com Errors-To: ML-ERRORS@fatcity.com From: "Orr, Steve" Subject: RE: OT: Guidelines/Standards for supporting non-oracle Organization: Fat City Network Services, San Diego, California X-ListServer: v1.0g, build 72; ListGuru (c) 1996-2001 Bruce A. Bergman Precedence: bulk Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2A09E.C53EF670" ------_=_NextPart_001_01C2A09E.C53EF670 Content-Type: text/plain; charset="iso-8859-1" You need a corporate data administrator nazi-type technocrat... A "data administrator" god not a mere database administrator dweeb. :-) Here's a long quote from a Tom Cox article: -------------------------------------- "The Data Administrator With the rise of data warehouses and data marts has come an increasing awareness of the strategic value of corporate metadata. Without good metadata, users and IS shops find it nearly impossible to compare data from different systems. Metadata is becoming the next battleground between database firms. And someone needs to be in charge of metadata: the data administrator. Identifying and empowering a formal data administrator will shorten data-warehouse project time lines and will improve the quality of data flowing through the organization. "Metadata is the connective tissue of information," says Mohit Sahgal of Andersen Consulting. "With it, the most far-flung applications in the organization can be tied together into a functioning whole. Without it, nothing will make sense." The data administrator must deal with the political reality that information is power. Just as banks have strict policies on the handling of cash--it must be checked in, checked out, counted, and tracked--so must information systems. We must treat information like banks treat cash. If some were to go missing, it must be clear who was responsible for it. Someone must set data-handling policies: Who enters new product numbers into the system? Who changes the format of product numbers? Who must be notified of format changes? What format will a new application use? These are the questions the data administrator must answer and then track the answers and audit compliance with policies. The data administrator finds out or assigns who owns which data elements and who can create, change, and delete what. If a regional database keeps a copy of the corporate master price list, then who is responsible for keeping that copy current--the price-list owner, who must then push changes in, or the application owner, who would have to poll for changes and pull them in? Do appropriate people have the right permissions to read the data they need? This implies, quite correctly, that the data administrator creates the security policy for the database, although others will likely implement it. " ------------------------------------------- -----Original Message----- Sent: Tuesday, December 10, 2002 3:23 PM To: Multiple recipients of list ORACLE-L Hi, I've made a lot of money over the years fixing Access databases as a consultant. They usually called me after being painted into a corner with a non-normalized, Excel spreadsheet looking thing. I have to diplomatically tell them that their baby is ugly. Then they can either pay me to fix it or say goodbye. If you start supporting these half-baked databases you probably (1) won't get paid any extra and (2) won't be able to say goodbye. Plus you just might pi$$ off some department head by telling them that their baby is UGGGGLLEEEE. Unless you get more resources with this extra 'little' tasking, you are going to feel some pain. Jerry Whittle ASIFICS DBA NCI Information Systems Inc. jerome.whittle@scott.af.mil 618-622-4145 -----Original Message----- At 01:15 PM 12/10/2002 -0800, Rick_Cale@teamhealth.com wrote: Hi, We are virtually an Oracle shop with 2-3 sql server databases due to 3rd-party software restrictions. We have been asked about supporting other "small" databases such as Access,etc within our company. My question is if you were asked to support "smaller" databases what restrictions/guidelines/standards are worth considering? Be kind-constructive answers only :-) ------_=_NextPart_001_01C2A09E.C53EF670 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: OT: Guidelines/Standards for supporting non-oracle

You need a corporate data administrator nazi-type = technocrat... A "data administrator" god not a mere database = administrator dweeb. :-)   Here's a long quote from a Tom Cox = article:

--------------------------------------
"The Data Administrator
With the rise of data warehouses and data marts has = come an increasing awareness of the strategic value of corporate = metadata. Without good metadata, users and IS shops find it nearly = impossible to compare data from different systems. Metadata is becoming = the next battleground between database firms. And someone needs to be = in charge of metadata: the data administrator. Identifying and = empowering a formal data administrator will shorten data-warehouse = project time lines and will improve the quality of data flowing through = the organization.

"Metadata is the connective tissue of = information," says Mohit Sahgal of Andersen Consulting. "With = it, the most far-flung applications in the organization can be tied = together into a functioning whole. Without it, nothing will make = sense."

The data administrator must deal with the political = reality that information is power. Just as banks have strict policies = on the handling of cash--it must be checked in, checked out, counted, = and tracked--so must information systems. We must treat information = like banks treat cash. If some were to go missing, it must be clear who = was responsible for it.

Someone must set data-handling policies: Who enters = new product numbers into the system? Who changes the format of product = numbers? Who must be notified of format changes? What format will a new = application use? These are the questions the data administrator must = answer and then track the answers and audit compliance with policies. =

The data administrator finds out or assigns who owns = which data elements and who can create, change, and delete what. If a = regional database keeps a copy of the corporate master price list, then = who is responsible for keeping that copy current--the price-list owner, = who must then push changes in, or the application owner, who would have = to poll for changes and pull them in? Do appropriate people have the = right permissions to read the data they need?

This implies, quite correctly, that the data = administrator creates the security policy for the database, although = others will likely implement it. "

-------------------------------------------


-----Original Message-----
From: Whittle Jerome Contr NCI [mailto:Jerome.Whittle@scott.= af.mil]
Sent: Tuesday, December 10, 2002 3:23 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: OT: Guidelines/Standards for supporting = non-oracle


Hi,
I've made a lot of money over the years fixing = Access databases as a consultant. They usually called me after being = painted into a corner with a non-normalized, Excel spreadsheet looking = thing. I have to diplomatically tell them that their baby is ugly. Then = they can either pay me to fix it or say goodbye.

If you start supporting these half-baked databases = you probably (1) won't get paid any extra and (2) won't be able to say = goodbye. Plus you just might pi$$ off some department head by telling = them that their baby is UGGGGLLEEEE.

Unless you get more resources with this extra = 'little' tasking, you are going to feel some pain.
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
jerome.whittle@scott.af.mil
618-622-4145
-----Original Message-----
At 01:15 PM 12/10/2002 -0800, = Rick_Cale@teamhealth.com wrote:

Hi,

We are virtually an Oracle shop with 2-3 sql server = databases due to
3rd-party software restrictions.
We have been asked about supporting other = "small" databases such as
Access,etc within our company.  My question is = if
you were asked to support "smaller" = databases what
restrictions/guidelines/standards are worth = considering?
Be kind-constructive answers only :-)

------_=_NextPart_001_01C2A09E.C53EF670-- -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Orr, Steve INET: sorr@rightnow.com Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).