Well, Oracle text does (dba just needed to have selected it). Scott schema does (ditto, dba just needs to have installed the demos) Autotrace - yes, be nice if it were there HOWEVER, on a production system - it shouldn't necessarily be there so. Maybe that is good. What would I change. Actually, many of those things I would change are being addressed - a better sqlplus that is still sqlplus (coming, code name 'raptor', previewed at OOW). Htmldb - that was a big one. Most of the things I would change are 'political', the DBA/Developer relationship (or lack thereof). The (sometimes) developer approach of 'I don't need to learn the database' There is so much in there - what I would change is peoples knowledge level of what is actually available. I would appreciate better error messages sometimes - I can usually figure them out, but.;) I'll publish this to see what others add - maybe some have been addressed and we can point it out - others, I'll file away for the days when I'm asked 'what would you add.' Application Lifecycle Management 11.52, 12.02, 12.21 and 12.53 and higher and Quality Center 11.52, 12.02, 12.21 and 12.53. Localized Versions of the UFT 12.53 Add-in for ALM When you install the UFT 12.53 Add-in for ALM on a computer with a localized operating system, you can select whether to install the Add-in the language of your. There are many different types of Agile tools out there. Some are free, some are paid, some are going by the new business model called “Freemium” in which you get a distilled version of the software but to get all the awesome features and scaleability you have to pay. And you rated our response. Oh, I could go on forever. Here are some: 1. SQL*Plus with a built-in tabular format output; useful for rows that span across many lines. No, Grid Control SQL Output just doesn't cut it; it's a static output of the entire table. It doesn't have the powerful SQL*Plus commands. An unloader utility that reads at the block level and dumps data as plaintext ASCII much faster than the SQ*Plus or Pro*C programs can do. I miss the SQL*Forms 3.0 (if anyone is old enough to remember that)which allowed me to do quick and dirty data entry screens for dat manipulations. And, sweet oh sweet, I could edit the INP files for quick modifications. Master detail forms were a snap. Separation of roles where DBA can see the data files, dictionary, etc., but not the actual data. A separate role will allow the data to be seen and allow privileges. A third account type will have access to audit trails only. I understand this is being addressed in Data Vault. PL/SQL compilation where the decision to make the dependent objects such as triggers, functions, etc invalid due to table alters are controlled by DBA. When a table column data type is modified, the dependednt objects are immediately modified; however, sometimes the changes to the table do not alter the contents of the object and it need not be invalidated. This will help immensly in keeping the uptime of the system. Batch commits. When I should be able to do a mass update but ask Oracle to commit at a certain frequency only. I could do this by cursors; but a simple SQL will be very useful. Something very similar to the commit frequency setting in COPY command. Conditional Shared Pool manipulations. Shared pool contains SQL statements that should have been aged out eons ago; but linger about and cause the ORA-4031 error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2018
Categories |