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_at_scott.af.mil
618-622-4145

> -----Original Message-----
> At 01:15 PM 12/10/2002 -0800, Rick_Cale_at_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 :-)
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Whittle Jerome Contr NCI
  INET: Jerome.Whittle_at_scott.af.mil

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_at_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).