Hi,

My monthly text files downloads (from mainfame) are regularly reaching the
2gig+. I usually import the file into Paradox but the database is starting
to reach the 2gig limit. Besides chopping off fileds from the Paradox file
(my crude way of handling the problem) what steps would the group recommend
if facing this issue? Is there software that cater for larger databases?

Thanks
Hilton

"Hilton" <get_chatting (AT) hotmail (DOT) com> wrote

if this is mostly going into one "line item" table, and archiving and/or
breaking into multiple tables aren't comfortable options, then you're a C/S
candidate..


--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

Hilton wrote:

If you are importing a single text file into a single Paradox table, my
guess is the table is very flat. If you normalize that table to elimintate
redundancy, you'll probably be able to get a lot more data captured. For
example, if the file is a list of orders, and for each order you have a
customer name, address, phone number, etc, you can break that out into an
orders table and a customer table, with a foreign key join.

This will require a little (or a lot) extra effort in the parsing of the
text file, since Paradox's built in import won't do this.

Yes, there are. In fact, I don't think dBase files (or FoxPro) have this
limitation. Have you tried importing as a dBase file instead? You can work
with dBase files within Paradox.

The other options are to move to an Open Source database server, like
Firebird, MySQL, or PostgreSQL, or a commercial database server like Oracle
or MS SQL Server. Paradox will be able to connect to these database servers
as a client for reporting, data entry, queries, etc.

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.

Hilton wrote:
You may wish to discuss your options with the corporate data-center. They
may be able to provide you with an ODBC data-link directly to the tables,
or to a query-result that is periodically replaced.

Failing that, your approach of putting the data into separate Paradox tables
may indeed turn out to be the best way. A script, in Python or whatever
(or even VB) could do the splitting.

If your data file is 'large and flat,' also don't overlook the dBase format.

----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep