For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
Please let me know what you think. We have added SQL*Plus support. See these web pages: SQL*Plus common commands: https://www.oracle.com/database/technologies/appdev/dotnet/odtvscodesqlplus.html SQL*Plus Reference: https://www.oracle.com/database/technologies/appdev/dotnet/odtvscodesqlplusref.html More features from the changelog: Changes in version 19.3.3 Connection Dialog enhancements: Set/Change the current schema, improved proxy user connection UI Improved connection failure detection with an option to reconnect Support for macOS connections to Oracle Autonomous Database over TLS Support for database connections using LDAP Browse other schemas ("Other Users" node) in Oracle Explorer tree control SQL History and Bookmarks Limited SQL*Plus support Detection and warning of unsupported SQL*Plus commands in scripts (and child scripts) SQL*Plus CONNECT command associates the file with a connection Preservation of all session associated properties from execution to execution Autocommit On/Off setting Autocompletion of SQL*Plus commands Autocompletion of procedure/function parameters Intellisense/Autocomplete performance enhancements Syntax coloring for SQL and PL/SQL keywords and SQL*Plus commands/variables Append new results to existing results window Toolbar buttons to cancel running query and to clear results window Setting to automatically clear results window after each execution Remember previous selections in some UI elements and offer as defaults Support for REFCURSOR variables and implicit cursors Visual Studio Code theme support for Light/Dark/High Contrast themes
Ricardo Giampaoli and Rodrigo Radtke have recorded a 2 Minute Tech Tip video based on this article. Watch it here
Nice work, It will reduce the time of integration process.
This is an elegant solution to address a common problem for any application that is dependent on external metadata.
As you correctly point out, the burden is still on the external interfaces that populates the generic inbound metadata table.
Your solution isolates "the source system" dependent details to create a classic "source system agnostic" data architecture for metadata integration.
However, there is still the much larger issue of Data Governance with a large organization. Oracle-Hyperion DRM is a tool to help organizations
manage the source system dependent nature of metadata to create a "normalized" view of an organizations metadata. The solution you present here
is a nice complement to DRM, which you also point out is another potential "external" data source. EPMA and more recently FDMEE
have native integration with DRM (without the need to understand DRM's API or DRM's Data Structures). I for one, would love to see how your
solution paired with DRM, where DRM acts as the central enterprise repository the entire organizations metadata management needs. How
about a DRM to Hyperion Planning IKM !!!!!.