D
dbeavon
Guest
>> Nice to know, that I have inherited a well-maintained database. Or maybe the prior DBA was thinking ahead by not messing with this stuff. The OE DBMS in versions prior to OE12 does a big disservice by not managing some basic statistics for SQL query optimization purposes. It seems to me that an OpenEdge DBA could do more harm than good by manually tinkering with this type of thing. They shouldn't be responsible for maintaining the internal statistics. (Perhaps they can try to make tweaks to the stats on a rare occasion, but should not be playing with it as a general rule). Think of statistics like another type of data that is stored in the database. It is meta-data ... but it is derived directly from the data itself. Do you really want any OpenEdge DBA to be in a position where they are regularly making changes to that type of data? When our SQL92 query plans get ugly, and it is because of statistics, then we normally discover that it is a result of "human" error on the part of either the dba or their home-grown scripts (ie. their scheduled maintenance operations). The first thing I do when I see long-running SQL92 queries is send out an email to the OE dba to see what they broke. ;-) In contrast, our MS SQL Server environment is HEAVILY relying on cost-based query plans and we virtually NEVER have any incidences where inaccurate statistics are creating malformed query plans. That stuff is not the responsibility of a DBA so there is less room for human error. Note that the DBMS in OE 12 is finally taking responsibility for managing its own statistics. See docs.progress.com/.../Autonomous-Update-Statistics.html
Continue reading...
Continue reading...