Microsoft Excel Add-In For ALM 12.2x and 12.5x. Click the relevant download link to download and install this add-in on your HP ALM client machine. Note that to install this add-in, you must log in with administrator privileges. Refer to the HP ALM Microsoft Excel Add-in Guide to review additional important installation instructions. Otherwise If the C: Program Files Common Files Mercury Interactive EXISTS then Close ALL internet explorer browser sessions. Navigate to C: Program.

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. How To Install Sandisk U3 Launchpad there. 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.'

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. Canon Mpc190 Driver Windows 7 64 Bit more.

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.

How about allowing the DBA to age certain SQLs, either explicitly or via some pattern matching or both. Ability to use different userids in unix for the oracle owner and the user whos owns the logs such as alert log, listerner log, crs log, etc. This will allow the separation of roles - the DBA can perform database maintenance but a different user owns the logs. Canon Printer Drivers Pixma Mp 800 Driver there.

So the oracle software owner can't delete logs. The process of logging can be performed by a root-owned process, installed during the execution of root.sh. There is more; but I leave it to others how they feel. Cross-platform data file incompatibility. With the size of databases these days export/import takes too long. Transportable tablespaces require 10g to cross platforms and have to go through an extra RMAN process--and as of 9.2.0.5 the process is still buggy. Single oracle.exe on 32-bit windows.

Context switching among threads may be faster, but the limits of addressable memory render this less imporant, even with the /3GB switch. 64bit Windows should address this, but not without upgrading hardware. Inability to bypass redo for statements that don't need recovery (for example, the insert /*+ append */ into the Hits table for Tom's pagination solution). Always writing above the high watermark can eat up space quickly and like a temporary tablespace, I don't care if I can't recover it. Create a new kind of tablespace of type unrecoverable and stick segments you don't care about here.