| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Large databases and MS Access
I'm not familiar w/the missing right parens problem you mention. It's got
its warts, no doubt--security of the physical datafiles is certainly one of
them--the lack of triggers is another. But in its space--local and
lan-based, single-tier apps w/relatively small volumes of data and/or low
numbers of concurrent writing users, it can make for very decent solutions.
There are projects for which msaccess is woefully inadequate. There are also projects for which a full-blown oracle app is overkill. If prejudice and available talent don't preclude you from considering either option, you have a better chance at giving the project its due.
Cheers,
-Roy
Roy Pardee
Programmer/Analyst
SWFPAC Lockheed Martin IT
Extension 8487
-----Original Message-----
Sent: Wednesday, April 16, 2003 12:06 PM
To: Multiple recipients of list ORACLE-L
So, y'all have never run into the "missing right parentheses" and other anomolies of MS Access? How's about the same version of Access and MDAC on two machines, one running NT, the other Tuke, each causing vastly different explain plans on the same .mdb? I won't even go into the former Access2K base of data here that refused to let anyone use it when it grew to 1.2GB (in this case "GB" != "Green Bay"). I also like the ability for users to delete the .mdb file from the OS level because you need OS level access to it in order to get to the data.
If it has a bad rep/rap, it's because it deserves it, IMHO. I can't wait until someone can prove ROI on an Oracle DW/DM, when we can chuck the MS Axxess of Evil.
Sorry. Had that MS Axxess thorn in my side twisting on me there...
Rich
Rich Jesse System/Database Administrator rich.jesse_at_qtiworld.com Quad/Tech International, Sussex, WI USA
-----Original Message-----
Sent: Wednesday, April 16, 2003 12:24 PM
To: Multiple recipients of list ORACLE-L
Ditto.
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...
Cheers,
-Roy
Roy Pardee
Programmer/Analyst
SWFPAC Lockheed Martin IT
Extension 8487
-----Original Message-----
Sent: Wednesday, April 16, 2003 7:19 AM
To: Multiple recipients of list ORACLE-L
Mark,
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
ASIFICS DBA
NCI Information Systems Inc.
jerome.whittle_at_scott.af.mil
618-622-4145
-----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: http://www.orafaq.net
--
Author: Jesse, Rich
INET: Rich.Jesse_at_qtiworld.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting servicesto: 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).
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting servicesto: 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). Received on Wed Apr 16 2003 - 16:09:16 CDT
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
 |
 |