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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2 gb database - then errors

Status
Not open for further replies.

Moss100

Technical User
Aug 10, 2004
586
GB
My database has now reached 2GB - It's access 2002. Do later versions let you have a bigger database or is it a problem with FAT 32?

Thanks for any help.

Regards Mark
 
Do you have a full blown RDBMS that you can put large tables in (something like Oracle or SQL server). If you can get your larger tables out that should buy you some time before you need to move the whole thing over.

Good LUck,

Alex

Ignorance of certain subjects is a great part of wisdom
 
Or for the more basic questions - all tables normalized? Do you do alot of deletes? (then you must compact and repair) Do you have forms/queries/reports not being used anymore? In developing a database, it's suggested you allow for archiving old data - do you/can you?
Having worked with AT&T before and after the split, it takes alot to have a database that large. You're talking about storing something like every phone call (all phones) made in the U.S.A. for two months.

 
Thanks guys - it's a photo database - I guess I'll have to start an archive. Thanks anyway for your help. Anyone any other thoughts?
 
One option depending on your application is store the path to the photo in the database and not the photo itself. But again, that depends on your application and how you are using/accessing the DB.

I tried to have patience but it took to long! :) -DW
 
fneily said:
" ... considering a photo is about 1mb ... "
... of course that depends on the imiage and some of how it has been treated from the source to it's current storage ... my daughter's newest camera takes up to 8 Meg Pixels at some otherwordly color depth ... single images in the range of an order of magnitude or so of this ...

No ()*&^(*#$&Y*(#@&VBF wonder she wants a B I G external HD for Christmas!!!




MichaelRed


 
There are methods to store pictures without bloating the database. I.e., the database only grows by roughly the size of the picture, as opposed to the "easy" way shown in Microsoft examples and "Access in 21 days" style books where 50K picture causes the database to grow by 400K - 500K.

Unfortunately I don't have the code handy, but it involves the GetChunk method in ADO.


 
I believe that access doesn't store compressed photo formats as jpg, but stores them uncompressed. Better way anyhow is to store the file location, as mentioned.

Good luck!

EasyIT

"Do you think that’s air you're breathing?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top