Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Large databases and MS Access

RE: Large databases and MS Access

From: Pardee, Roy E <>
Date: Wed, 16 Apr 2003 09:23:43 -0800
Message-ID: <>


I think msaccess gets a bad rap b/c it's approachable enough that folks who don't really know what they are doing can & do wade in & make messes. But that's an issue w/the developer, not the tool. Access has declarative referential integrity, a fairly full SQL implementation (including some nice extensions) & a really great forms engine (puts vb to shame IMHO). You can put a crapplication together w/most any tool...

But alas, ms seems to be pushing mssql at the expense of msaccess & so I won't be surprised if msaccess doesn't go the way of the dodo in time...



Roy Pardee
SWFPAC Lockheed Martin IT
Extension 8487
-----Original Message-----

Sent: Wednesday, April 16, 2003 7:19 AM
To: Multiple recipients of list ORACLE-L

MS Access has been very, very good to me. In other words, I've made much more than a pocketful of change working with it. True an Access 'DBA' doesn't have to worry about tablespaces, extents, etc., like an Oracle DBA but there are a many things in common such as relationships, table design, and indexing. Also your Access 'DBA' is usually the developer of the SQL, modules, forms and reports. In some small businesses, the Access 'DBA' is also the SA. In many cases, an Access professional knows a whole lot more about databases than someone who is only a DBA. I've built Access databases, including equipment and training, used to run small companies for much less than the cost of one Oracle license alone. I've also quickly built Access databases for large companies where the database shop would say things like "Disapproved. Please resubmit in 90 days for final disapproval."
It's a matter of the right tool for the job. A sledgehammer is an inferior tool compared to a hammer for driving in a nail. BTW: Compress has nothing to do with tuning. Think of Access as having autoextending datafiles set. Compressing is similar to ALTER DATABASE DATAFILE RESIZE to slim things down. If anything, frequent compressing shows a need to do some tuning as inefficient SQL can cause was Access people call 'bloat'.
Jerry Whittle
NCI Information Systems Inc.
-----Original Message-----

I have a friend her calls herself an Access DBA. I just smile politely and say nothing. Apparantly you can back them up using Windows Explorer (or the DOS copy command) and there is a "Compress" option in Access for tuning... she runs that one each week. I just wish Oracle could simplify their tuning to a single menu option! :-) On the plus side I feel safe in the knowledge that if a company ever looked at "Access DBA" on a resume and didn't laugh then I'm probably not interested in working there anyway.

Please see the official ORACLE-L FAQ:

Author: Pardee, Roy E

Fat City Network Services    -- 858-538-5051
San Diego, California        -- Mailing list and web hosting services

To REMOVE yourself from this mailing list, send an E-Mail message
to: (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). Received on Wed Apr 16 2003 - 12:23:43 CDT

Original text of this message