Can I create tables/indexes?

jgustafson

New Member
I have been reading some other posts where you have cautioned people from creating tables/indexes OR maybe you were cautioning to not run these outside of the progress db administrator?

I am TOTALLY new to the progress database. I have figured out how to run queries, create exports, etc.

Having a problem with a query/export that I am trying to create. I think it is due to the software vendor data structure. I can join 2 tables together and get results in 3 minutes. I join the 3rd table whose primary index is date/time and the query goes to breakfast/lunch/dinner and more. It doesn't look like i can join back to the empid in the 2 tables. I can join on the barId from table 3, but I think i am reading 1 record from 2 tables and the all of table 3's records for that one read.

Thus i would like to create my own table, with data from the 3rd table, date, time, barId. This barId is an index back on one of the 2 tables.

I then can create a subset of the data that I need to work with. And not touch the vendors data structure.

Thank you
J
 
Read up about temp-tables. This allows you to create tables which last for the duration of the session. They are very handy for reporting, among many other uses. They work out of memory, as long as they fit, and then dynamically expand to disk, so they are also very fast and efficient. This sounds like a case where you might be able to fill the table in two passes, each efficient to the data set and then use the temp-table for the report. You could also look into ProDataSets for having multiple tables with defined relationships ... assuming your version of Progress is sufficiently modern.
 
Thank you for reply - i will take a look at your suggestions.
Can you tell me if this is an on going process - daily right now. I wanted to do this every hour, but was not successfull at manipulating the process time in sql. Do you still suggest a temp table? Or will I make a mess of the disk space defined to the database? Or is the temp space defined in one area?

Version 9.1D (I think that is fairly current?)

J
 
First, 9.1D is ****FAR**** from current. Aside from 9.1E, we have had three releases of 10.0 and are about to get the third release of 10.1 and will have 10.2 this year, so 9.1D is actually painfully ancient.

Next, we have the problem that this is SQL. You might want to move to that forum.

The first problem is that the temp-tables of which I speak are a feature of ABL, not SQL.

I believe that there is some kind of SQL temp table thing in more recent versions, but I doubt they are in 9.1D.

You could look into creating a view which did the join, but that is going to rely on the existing indexes for performance.
 
Back
Top