How to standardize and centrally manage connection definitions?
(Doc ID 804175.1)
Last updated on DECEMBER 12, 2019
Applies to:
Oracle SQL Developer - Version 1.5.4 to 3.2Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Goal
When a connection is defined in SQL Developer, the definition is stored locally in the sub-directory where SQL Developer resides.
Some customers may face maintenance issues as new databases are added to their infrastructure, and as changes are made on the server side that would affect previously defined connections. As the number of seats and the number of databases grows, maintenance of each developer's connection definitions becomes more problematic.
Is there a way to store the connection definitions for SQL Developer so that they can be standardized across the enterprise and be centrally managed and located?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |