
Matthew Marcus (Customer) asked a question.
Why is progress database so slow to dump the schema?
We have 1000 tables. Why does it take a 60s to generate a .df file, whereas if I used a SQL schema dump it would be done in seconds?

Matthew Marcus (Customer) asked a question.
We have 1000 tables. Why does it take a 60s to generate a .df file, whereas if I used a SQL schema dump it would be done in seconds?
How do you connect to the database?
I believe it's
-b -i -noinactiveidx -db name -H host -S port
Compare this to shared memory connections. The schema dump uses the join queries. Does your version of Progress support server-side joins?
I could, but that's not a restriction we'd like to introduce in our case. And to keep the apples to apples comparison, SQL is fast over the network too even :).
I checked our DB: Database server side join support (-ssj): Enabled
Like, why couldn't I just make a SQL based version to make the same DF?
Joins for ABL and SQL are different mechanisms, but they produce the same results. As I mentioned before, test is simple: connect to the database without the -H/-S parameters.
The ABL code can be fast for remote connections without using server-side joins, but the schema dump was not written with this goal in mind.