MicroSoft Support Limitations, etc.

C

CptCrusty1

I'm trying to find out what Microsoft Officially supports in terms of the
size of Access db's. I.e. If you have questions for MS, they say no since
your db tables are over a certain size, or you have over x users in a given
db. Published numbers are such:

2GB for db size, 255 users. I heard from a friend of a friend of a friend,
that if your tables are over 65000 records, MS won't give you any assistance.

We have some tables with over 1 million records (and some even larger) and
I'm am building a proposal for converting the larger tables to Oracle and
need supporting documentation.

Thanks.
Crusty.
PS, no email to me please...
 
G

Graham R Seach

Why do you want Microsoft support? You can get the help you're likely to
need right here.

Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
(Currently in Japan)
 
J

Joan Wild

CptCrusty1 said:
I'm trying to find out what Microsoft Officially supports in terms of the
size of Access db's. I.e. If you have questions for MS, they say no since
your db tables are over a certain size, or you have over x users in a
given
db. Published numbers are such:
Click to expand...

I've not heard of any such limitations. Furthermore, going over the limits
doesn't really have to do with support, it means it won't work at all.
2GB for db size, 255 users. I heard from a friend of a friend of a
friend,
that if your tables are over 65000 records, MS won't give you any
assistance.
Click to expand...

Rubbish.
 
C

CptCrusty1

I have an Access Macro that runs a BUNCH of stuff. It uses Multiple ODBC
calls to an Oracle db to bring data in and create tables. It then uses the
new tables and joins them to more Oracle tables via ODBC and creates another
table... yadda yadda. The entire process is like this. For the first set of
tables, I created a pass-through query which is MUCH more efficient on the
order of about 3600% faster, however this is only 1 PT query of the 10 or so
that I could write. I'd like to tell the ORacle group that the whole thing
should be built as a Store Procedure with view calls, etc., but I need
supporting documention to demonstrate the efficiency of Oracle vs.
Access...at least in this particular case. The Oracle gods are a little
hard-headed and stingy with their toys. LOL

Thanks.
Crusty
 
A

Albert D.Kallal

I need
supporting documention to demonstrate the efficiency of Oracle vs.
Access

You seem to hint that your data store is now Oracle. This means that your
limitations are that of oracle..and not ms-access anymore.

I don't see why you can't use pass though queries, or even better, simply
execute oracle commands from ms-access to create the stored procedure.

And, further, why use ms-access to create stored procedures on the oracle
side. Get the oracle procedures written, and then call them from ms-access.

You should only be returning the results you need to ms-access.
 
Top