Discussion:
del * from x where zip < 14500
(too old to reply)
v***@at.BioStrategist.dot.dot.com
2014-04-03 06:48:14 UTC
Permalink
I broke up the 6gb file and now the mdb can't be opened to append to,
so I'm figuring I need to shrink it (its 2gb) to append the pieces.

Can I make a "query" that deeletes?


- = -
Vasos Panagiotopoulos, Columbia'81+, Reagan, Mozart, Pindus, BioStrategist
http://www.panix.com/~vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---
[Homeland Security means private firearms not lazy obstructive guards]
[Urb sprawl confounds terror] [Phooey on GUI: Windows for subprime Bimbos]
John W. Vinson
2014-04-03 19:45:45 UTC
Permalink
Post by v***@at.BioStrategist.dot.dot.com
I broke up the 6gb file and now the mdb can't be opened to append to,
so I'm figuring I need to shrink it (its 2gb) to append the pieces.
Can I make a "query" that deeletes?
- = -
Vasos Panagiotopoulos, Columbia'81+, Reagan, Mozart, Pindus, BioStrategist
http://www.panix.com/~vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---
[Homeland Security means private firearms not lazy obstructive guards]
[Urb sprawl confounds terror] [Phooey on GUI: Windows for subprime Bimbos]
You can, but it won't help. Deleting records from a table does NOT free up the
space that those records occupied until you Compact and Repair the database.

Try compacting; if that doesn't work try creating a new database and importing
(selectively).

6GByte is HUGE - how big are your tables? Tens of millions of records? Are you
storing images or attachments in the tables? They can take up a lot of room,
and depending on your version of Access may not be handled efficiently. It's
often better to store images or attachments (.pst files, Word documents, etc.)
just as external files in a folder and store the filename and path in your
table, with (simple) code to launch the application which can read the files.
--
John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://answers.microsoft.com/en-us/office/forum/access?tab=question&status=all
http://social.msdn.microsoft.com/Forums/office/en-US/home?forum=accessdev
and see also http://www.utteraccess.com
v***@at.BioStrategist.dot.dot.com
2014-04-10 19:33:16 UTC
Permalink
It came zipped on a CD but opened to 6GB.
"wc -l" says I have 15 million records.
THe first time I used a different zip program and it opened
up only about 2.5GB and Access read all of that in.
On the full 6GB file I got nowhere.
So I broke it up to 2GB segments using GNU split.
I figured if I deleted the
records I don't want, I could add the rest in piece by piece.

But compacting seems a good ides. Becasue the 2.5GB was not that big as
an mdb.
I'm not sure what I did differently this time that it made such a big mdb.
(ie the fisrt time it made like a 500MB mdb from 2.5GB csv,
but now it made 2gb from 2gb).

Much obliged



- = -
Vasos Panagiotopoulos, Columbia'81+, Reagan, Mozart, Pindus, BioStrategist
http://www.panix.com/~vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---
[Homeland Security means private firearms not lazy obstructive guards]
[Urb sprawl confounds terror] [Phooey on GUI: Windows for subprime Bimbos]
John W. Vinson
2014-04-11 01:41:05 UTC
Permalink
Post by v***@at.BioStrategist.dot.dot.com
It came zipped on a CD but opened to 6GB.
"wc -l" says I have 15 million records.
THe first time I used a different zip program and it opened
up only about 2.5GB and Access read all of that in.
On the full 6GB file I got nowhere.
So I broke it up to 2GB segments using GNU split.
I figured if I deleted the
records I don't want, I could add the rest in piece by piece.
But compacting seems a good ides. Becasue the 2.5GB was not that big as
an mdb.
Sorry, but it's TOO BIG to be a .mdb. From the A2007 (applies to all versions
after 1.1) HELP file, first topic under Specifications:

Access database (.accdb) file size 2 gigabytes, minus the space needed for
system objects
Note NOTE: Although the maximum size for a single database file is 2GB,
you can work around this limitation by using a split database. A front-end
database file can point to thousands of back-end database files, each of which
could be as large as 2GB. For more information, see the topic, Split a
database.
--
John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://answers.microsoft.com/en-us/office/forum/access?tab=question&status=all
http://social.msdn.microsoft.com/Forums/office/en-US/home?forum=accessdev
and see also http://www.utteraccess.com
Loading...