Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

large database file size as a result of table addition 4

Status
Not open for further replies.

aonefun

Technical User
May 21, 2007
79
US
I have added a table to my database that is causing the database size to grow tremendously. There are a total of 807,000 records of zip codes along with corresponding latitude, longitude, city and state names.

I have set Unicode Compression to YES by all text fields. What other settings or actions will help reduce database file size?
 
I failed to mention that I have also compacted the database but it only helped a drop.
 
Have you compacted? Even tho that is large, it doesn't see THAT large. Do you have an Index on any of the fields (should be on any fields you are searching on)? A primary key? Subdatasheet set to NONE?

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at
 

How do you define "grow tremendously"? Different data types of numeric values, consume different size on disc. Text takes just as much as it needs no matter of field size. Would you share that info (field value & field data type) of your records?
 
Are you deleting/adding any table info to other tables? Are you creating alot of macros? Are you creating/changing alot of queries?
Not just data increases the size of a database. You must tell us everything you're doing.
 
My database was 2 mb until I added a POSTAL_CODE table. It then jumped to 49 mb, even after compacting the database.

The POSTAL_CODE table conains 4 TEXT fields and totals 800,000 records as follows:

POSTAL_CODE- field size: 7,Indexed: Yes, Unicode compression: Yes

LATITUDE- field size: 11, indexed: No, Unicode compression: Yes

LONGITUDE- field size: 11, indexed: No, Unicode compression: Yes

STATE- field size: 2, indexed: Yes, Unicode compression: Yes


Should we attribute this table's large file size based on the high record count of 800,000 or is this based on the table's settings, or ....
 
Sorry, but 49 mb is a SMALL database size ...
Less than 59 bytes added per row don't seem reasonable ?
 
It takes forever to upload, that's all. Wondering as follows:

Is there anything out there which would allow me to upload individual access database tables versus the complete database. This POSTAL_CODE table will not be changing so it can remain unchanged on the server. All other tables of small file size will be changing and require routine uploads.
 
backing it up to the internet on my site's server.
 

I would export txt files of changed tables, zip them and then upload.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top