If you want to really be aboe to tune the other 99% of the queries out there, knowledge of lots of stuff - physical storage mechanisms, access paths, how the optimizer works - thats the only way. They APPEAR to be able to tune a much larger percent but that is only because the people using these tools never look at the outcome - hence they continue to make the same basic mistakes over and over and over. They work using rules (heuristics) and can tune maybe 1% of the problem queries out there. There are tons of these tools on the market. You are not needed in this process, anyone can put a query in, get a query out and run it to see if it is faster. If you want a 10 step guide to tuning a query, buy a piece of software. But, what invariably happens is that the installer gets staged by itself, and the docs remain on the PC of the acquisition POC if they are ever even downloaded by them.Here is a short extract from a book I am working on. If the different teams would keep the docs with the installers, then we could at least see the relationship there. The association of the file name to the software version is not even in the release notes or the About info or the Help. So, why don't you put the software version that everyone can relate to in the file name? That other version string does not convey the information that we need, that it is 16.1 or whatever version. To figure out the software version, we have to execute the installer to find out what's in it and then keep our own notes about it.
We have several enclaves where TOAD is to be installed, and they are not all to be the latest version. or we have to actually run the installer and get a bit into it before we find out.
Either we have to keep track of the relationship of TOAD installer file names to product versions. So, the file version is not the product version as known in the wild. I cannot find anywhere in TOAD that 16.1 is referred to as 2022R3. I had the file "Toad_for_Oracle_2022R3_圆4_Full.exe", but I had to execute the installer and get to the (I think) third screen to confirm that it was indeed 16.1. Today, I was asked to provide my company a copy of TOAD for Oracle 16.1. The TOAD for Oracle installer executable does not have the product version (16.1) in its name. I have started to complain about this several times in the last year or so but have always checked myself.
0 kommentar(er)
