Question why small size?
- Thread starter marianne
- Start date
my question was "why is microsoft access database created with only 2 gigabyte size limit?" and your answer is "That is the address range of a 32 bit processor. Also a long integer."
What do you mean about your answer? do you mean that the size of 2 gigabyte of ms access file is due to address range of a 32 bit processor? what does that mean?
What do you mean about your answer? do you mean that the size of 2 gigabyte of ms access file is due to address range of a 32 bit processor? what does that mean?
RainLover
VIP From a land downunder
- Local time
- Tomorrow, 10:05
- Joined
- Jan 5, 2009
- Messages
- 5,031
A 32 bit processor cannot address more than 2 gb.
Access 1.0 was written in a long time ago.
I believe Microsoft would prefer you to go to SQL Server if you want bigger.
But that does not stop you from having more than one back end.
Do you have a problem that I can help with or are you just curious.
Access 1.0 was written in a long time ago.
I believe Microsoft would prefer you to go to SQL Server if you want bigger.
But that does not stop you from having more than one back end.
Do you have a problem that I can help with or are you just curious.
can I ask you a question? for example I am just a small business who would like to store business records using simple database. So I dont need sql server on my desktop because its just pretty little. but my record will go up to 50 gig or so.
I am also wondering, if I am right, SQL database file is in MDF file format. it is just a simple one file also just as MDB file for access. Maybe its just because of the engine that SQL or other SERVER uses that can accomodate huge size database.
Why wont they improve the engine of access so it can also accomodate huge file databasing?
Why wont they improve the engine of access so it can also accomodate huge file databasing?
RainLover
VIP From a land downunder
- Local time
- Tomorrow, 10:05
- Joined
- Jan 5, 2009
- Messages
- 5,031
Marianne
I can't say with full authority. But Access was first developed as a small desktop application. I fell as though it has far exceeded Microsoft's expectations.
2 Gig is a pretty big database. But if that does not suit your need then Microsoft has a free version of SQL Server but I think it is limited to 5 users.
Other than that you can go to MySQL. This is totally free and is not a big jump as far as a learning curve is concerned. You can still use your MS Access front end with very little interruption.
I can't say with full authority. But Access was first developed as a small desktop application. I fell as though it has far exceeded Microsoft's expectations.
2 Gig is a pretty big database. But if that does not suit your need then Microsoft has a free version of SQL Server but I think it is limited to 5 users.
Other than that you can go to MySQL. This is totally free and is not a big jump as far as a learning curve is concerned. You can still use your MS Access front end with very little interruption.
Rich
Registered User.
- Local time
- Today, 23:05
- Joined
- Aug 26, 2008
- Messages
- 2,876
Any db that's in excess of 2gig is either poorly designed or is not a small business
that's is what I've been telling all along to other users I have known. MS Access has far exceed Microsoft's expectations. Therefore, there is a need for improvements for its full potential.
as I have said, it would be impractical for me to use sql or any other servers on my computer if my business is just small. for example, I make a program from access and sold it to a small business enterprise. I dont think it is practical to install a server in a single computer for their usage.
I just see simple is easy and beautiful.
as I have said, it would be impractical for me to use sql or any other servers on my computer if my business is just small. for example, I make a program from access and sold it to a small business enterprise. I dont think it is practical to install a server in a single computer for their usage.
I just see simple is easy and beautiful.
I say it is still small business because, the generated income is just small but the records are voluminous and the business stayed for many years now that it had accumulated many records during their business life.
http://www.access-programmers.co.uk/forums/editpost.php?do=editpost&p=834099
http://www.access-programmers.co.uk/forums/editpost.php?do=editpost&p=834099
While I'm in no position to say with any certainty whether 640 KB... erm, sorry excuse me, 2 GB, is good enough for anyone-
For small business that didn't have the luxury & money to buy a server and licenses required to support such, I would have recommended MySQL or PostgreSQL as a data store with Access as a front-end client. In fact that's how it was done for the last nonprofit company I worked for, though it wasn't for the want of size but rather for want of transactions*, logging*, and remote access without spending a penny and making do with old hardware.
* To be clear, both can be done inside a pure Access solution but require additional implementation and codes to support such functionality; but I say why re-invent the wheel?
Anyway, so to me, Access's 2GB size limit is quite reasonable when we're looking at it as a desktop solution. But as soon as a business take it up and make it their critical mission application, they will have to be prepared to support it which may include taking it beyond its capabilities by enabling a backend capable of addressing more than 2 GB.
For small business that didn't have the luxury & money to buy a server and licenses required to support such, I would have recommended MySQL or PostgreSQL as a data store with Access as a front-end client. In fact that's how it was done for the last nonprofit company I worked for, though it wasn't for the want of size but rather for want of transactions*, logging*, and remote access without spending a penny and making do with old hardware.
* To be clear, both can be done inside a pure Access solution but require additional implementation and codes to support such functionality; but I say why re-invent the wheel?
Anyway, so to me, Access's 2GB size limit is quite reasonable when we're looking at it as a desktop solution. But as soon as a business take it up and make it their critical mission application, they will have to be prepared to support it which may include taking it beyond its capabilities by enabling a backend capable of addressing more than 2 GB.
editolis
Panathinaikos Fun
- Local time
- Tomorrow, 01:05
- Joined
- Oct 17, 2008
- Messages
- 107
If any of your tables is more than > 2 gbytes then you have to go to Oracle or to SQL Server.
The other option is to split your database and to create 2 or 5 or 10 or 20 (or i do not know how many) databases as a back end, each one heaving 1 or 5 or 10 tables with the maximum size of 2 gbytes per mdb.
The other option is to split your database and to create 2 or 5 or 10 or 20 (or i do not know how many) databases as a back end, each one heaving 1 or 5 or 10 tables with the maximum size of 2 gbytes per mdb.
- Local time
- Today, 23:05
- Joined
- Sep 12, 2006
- Messages
- 16,072
marianne
i really cannot believe you can have a "normal" data requirement of 50Gb. do you mean 50Mb by any chance?
there is something seriously amiss if you think you require that much storage,
either that, or you are a major plc, in which case you must have a substantial IT dept in your company.
-------
2Gb is NOT small - it is absolutely enormous for most general purposes.
i really cannot believe you can have a "normal" data requirement of 50Gb. do you mean 50Mb by any chance?
there is something seriously amiss if you think you require that much storage,
either that, or you are a major plc, in which case you must have a substantial IT dept in your company.
-------
2Gb is NOT small - it is absolutely enormous for most general purposes.
Similar threads
