I asked our IT department to do UPDATE STATISTICS on a restored progress database (open edge 10.1) , on all tables and indexes
How do I see if this process completed succesfully?
If I do a SELECT * FROM sysprogress.systblstat it shows me zero (0) records now.(before UPDATE STATISTICS has ran)
If UPDATE STATISTICS ran succesfully this table should contain "some" records???
That is correct, you should see data in those tables.
They either didn't run it or someone forget to add COMMIT WORK to the script.
Mhhh my DBA tells me now that there is no such thing as STATISTICS on Progress (installed on AIX) because it consists of flat files
Is this true? I have considerable douts??
Mhhh my DBA tells me now that there is no such thing as STATISTICS on Progress (installed on AIX) because it consists of flat files
>
Is this true? I have considerable douts??
Is he actually a Progress DBA? I doubt that anybody around here would consider Progress to be a flat file based DBMS.
And yes, since Version 9 dot something there are statistics available that are used for SQL query optimization.
Your are either misunderstanding your DBA or he is very, very wrong.
A "flat file" is: http://www.techterms.com/definition/flatfile
"A flat file database is a database
that stores data in a
plain text file. Each line of the text file holds one record, with
fields separated by delimiters, such as commas or tabs. While it uses a
simple structure, a flat file database cannot contain multiple tables
like a relational database can...."
That does not describe a Progress database. If you were to use a text
editor to look inside a Progress db you definitely would not see
anything like this (if you do do so do NOT save the file when you exit
the editor -- you will corrupt your db if you do).
Progress is a relational database which stores tables and indexes in a
complex structure spread across many files that are themselves
potentially spread across many paths and devices.
Progress also most definitely does support statistics for the SQL
engine. Your DBA /might/ be trying to say that the 4GL engine is
statically optimized (indexes are selected at compile time without
reference to statistics for 4gl programs). The database supports both
4gl and SQL access so if your DBA is only familiar with the 4gl he might
not be aware of the SQL capabilities.