Paradox Community

Items in pnews.paradox-client_server

Subject:Re: Best way to Add from Paradox Table to AWS Postgres Table
Date:Mon, 11 May 2020 12:03:12 +1000
From:Tom Krieg <>
The speed problem lies in the fact that you're directly linking Paradox 
to a SQL database. No matter what you do, if you don't separate Paradox 
and Postgres you'll have issues because the BDE has to work out the SQL 
statements. What you're seeing is one full transaction with commit per 
record and that is very inefficient. Python's not going to help you 
because it's still one transaction per record. What you want is ONE 
transaction with a commit every 500 or 1000 records and you can only do 
that with SQL, not Paradox.

On 10/05/2020 7:28 pm, Robert MacMillan wrote:

> The current method works just fine but but is just slow. Maybe none of 
> the other methods are going to be any faster as the speed problem is 
> possibly related to the insert - commit at the AWS end.

Copyright © 2004