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.
[EMAIL PROTECTED]
618-622-4145
-----Original Message-----
At 01:15 PM 12/10/2002 -0800, [EMAIL PROTECTED] 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 :-)
