table/database size

[SalimShahzad]

dear respected gurus,

i have been working several years in access, but the size of db reaches
till 250MB max. now we have one very big projects where we will have
hundred of thousdands of records.

so i had read a lot on this group in access 97 the limit of tables/db
size was 1Gb, it increase to acc2k 2Gb , then same for acc2002, then
again same for access 2003

so since long time version releaseing but Microsoft has not increase
the limits.as i had check access specifications

also on network enviornment, if i split apps in access 2 mdb,one as
backend one as front. can i utulize ms sql server or msde sql edition.
but could nt find any way how to access using odbc or else best method
on network

i have a huge insurance data, that will convert in oracle later stage.
can any one my respected GURUS advise/put some highlights on that

Thanks & Regards,
Salim Shahzad

[Trevor Best]

SalimShahzad wrote:

dear respected gurus,

i have been working several years in access, but the size of db reaches
till 250MB max. now we have one very big projects where we will have
hundred of thousdands of records.

so i had read a lot on this group in access 97 the limit of tables/db
size was 1Gb, it increase to acc2k 2Gb , then same for acc2002, then
again same for access 2003

so since long time version releaseing but Microsoft has not increase
the limits.as i had check access specifications

also on network enviornment, if i split apps in access 2 mdb,one as
backend one as front. can i utulize ms sql server or msde sql edition.
but could nt find any way how to access using odbc or else best method
on network

i have a huge insurance data, that will convert in oracle later stage.
can any one my respected GURUS advise/put some highlights on that

MSDE will be no good, it has the same 2GB limitation, you need SQL
Server Standard edition or above to get a big database.

If you're going to upgrade to Oracle later then why wait? Do it now.
Doing something different in the meantime will be a waste of time and
resources as all will have change when you upgrade again later.
--
This sig left intentionally blank

[SalimShahzad]

dear sir,

the issue is that we have to merge all 3 insurance companies data in
one at access plateform. as access is already running 10 yrs on our
network. now there is some new insurance application coming that will
migrate all access data to oracle. so migration part is for them.

now our part to merge the headeche.

i had used as trial MSDE, looks and feels is same like ms sql server 2K

but as you said 2Gb still the limit so i think better to look another
db...well what is ur opnion if v used split db in various say db1 has
some tables upto 2Gb then db3 has 2Gb

regards,
salim shahzad

[Trevor Best]

SalimShahzad wrote:

dear sir,

the issue is that we have to merge all 3 insurance companies data in
one at access plateform. as access is already running 10 yrs on our
network. now there is some new insurance application coming that will
migrate all access data to oracle. so migration part is for them.

now our part to merge the headeche.

i had used as trial MSDE, looks and feels is same like ms sql server 2K

but as you said 2Gb still the limit so i think better to look another
db...well what is ur opnion if v used split db in various say db1 has
some tables upto 2Gb then db3 has 2Gb

You can split into several MDBs (or MSDE databases for that matter). I
don't know of any other database that will handle large amounts of data
without paying a lot for it.

--
This sig left intentionally blank

[Elaine]

Salim,

It would be much, much, much, much, much better to do the conversion
on Oracle.

Create Oracle tables to hold the legacy data and use the legacy
frontends to connect to Oracle. ADO and dsnless connections work
great for this, even in Access 97 with the correct drivers. Get the
Oracle OLEDB driver from Oracle; don't use Microsoft's. If you're
going to use ODBC make sure to use the Microsoft version
2.573.something, or later.

Potential problems occur when Access table and column names do not
meet Oracle naming and length standards. Memo columns are also
problematic; how usable they will be in Oracle depends upon how the
Oracle columns are defined for the Access memo columns. Your dba and
application developers will have to discuss the options and determine
which options will work best in your situation.

After all the legacy data is working on Oracle with the legacy apps,
spend as much time as it takes to get the new structures working and
populated.

Oracle is AWESOMEm btw.

HTH,
Elaine

On 20 Mar 2005 05:38:56 -0800, "SalimShahzad" <sa**********@gmail.com>
wrote:

dear sir,

the issue is that we have to merge all 3 insurance companies data in
one at access plateform. as access is already running 10 yrs on our
network. now there is some new insurance application coming that will
migrate all access data to oracle. so migration part is for them.

now our part to merge the headeche.

i had used as trial MSDE, looks and feels is same like ms sql server 2K

but as you said 2Gb still the limit so i think better to look another
db...well what is ur opnion if v used split db in various say db1 has
some tables upto 2Gb then db3 has 2Gb

regards,
salim shahzad