- Oracle Sql Developer Alternatives For Mac Pro
- Oracle Sql Developer Alternatives For Mac Download
- Oracle Sql Developer Tool
Important: If you are using a pre-release (Early Adopter) version of SQL Developer, and if you want to be able to continue to use this pre-release version after installing the official release kit, you must unzip the official release kit into a different directory than the one used for the pre-release version. If Oracle Database (Release 11 or later) is also installed, a version of SQL Developer is also included and is accessible through the menu system under Oracle. This version of SQL Developer is separate from any SQL Developer kit that you download and unzip on your own, so do not confuse the two, and do not unzip a kit over the SQL Developer files that are included with Oracle Database. Suggestion: Create a shortcut for the SQL Developer executable file that you install, and always use it to start SQL Developer.
For Windows systems, there are two kits: one for systems on which the Sun Java SDK release 1.5.006 or later is installed, and another for systems with no Java SDK or a Sun Java SDK release earlier than 1.5.006. Be sure to download the appropriate kit. Before you install SQL Developer, look at the remaining sections of this guide to see if you need to know or do anything else first.
The steps for installing SQL Developer depend on whether or not you will be using it on a Windows system that does not have the Sun Java SDK release 1.5.006 or later installed:. For a Windows system with the Sun Java release 1.5.006 or later installed, follow the instructions in. For all other systems (Linux and Mac OS X systems, and Windows systems with no Java SDK or a Sun Java SDK release earlier than 1.5.006 or later installed), follow the instructions in. 1.2.1 Windows Systems with JDK5.0 To install and start SQL Developer on a Windows system on which the Sun Java J2SE JDK 5.0 (Update 6 or later) is installed, follow these steps:. Unzip the SQL Developer kit into a folder (directory) of your choice (for example, C: Program Files).
This folder will be referred to as. Unzipping the SQL Developer kit causes a folder named sqldeveloper to be created under the folder (for example, C: Program Files sqldeveloper).
It also causes many files and folders to be placed in and under that directory. To start SQL Developer, go to sqldeveloper, and double-click sqldeveloper.exe.
If you are asked to enter the full pathname for java.exe, click Browse and find java.exe. For example, the path might have a name similar to C: Program Files Java jdk1.5.006 bin java.exe. After SQL Developer starts, you can connect to any database by right-clicking the Connections node in the Connections Navigator and selecting New Connection. Alternatively, if you have any exported connections (see or ), you can import these connections and use them. You can learn about SQL Developer by clicking Help, then Table of Contents, and reading the help topics under SQL Developer Concepts and Usage.
1.2.2 Linux and Mac OS X Systems, and Windows Systems without JDK 5.0 SQL Developer requires that the Sun Java J2SE JDK 5.0 (Update 6 or later) be installed on the system. If you need to install this JDK, go to and click the link for downloading JDK 5.0 Update 12 (or the most recent available update). To install and start SQL Developer, follow these steps:.
Unzip the SQL Developer kit into a directory (folder) of your choice. This directory location will be referred to as. Unzipping the SQL Developer kit causes a directory named sqldeveloper to be created under the directory. It also causes many files and folders to be placed in and under that directory. To start SQL Developer, go to the sqldeveloper directory under the directory, and do one of the following, as appropriate for your operating system: On Linux and Mac OS X systems, run sh sqldeveloper.sh.
On Windows systems, double-click sqldeveloper.exe. After SQL Developer starts, you can connect to any database by right-clicking the Connections node in the Connections Navigator and selecting New Connection. Alternatively, if you have any exported connections (see or ), you can import these connections and use them.
You can learn about SQL Developer by clicking Help, then Table of Contents, and reading the help topics under SQL Developer Concepts and Usage. Note: Migration of user settings is supported only from SQL Developer Release 1.1.3 or later to Release 1.5. These settings refer to database connections, reports, and certain SQL Developer user preferences that you set in a previous version by clicking Tools and then Preferences. However, some user preferences are not saved, and you must re-specify these using the new release. To migrate user settings from a previous SQL Developer release:. Unzip the Release 1.5 kit into an empty directory (folder).
Do not delete or overwrite the directory into which you unzipped the kit for the previous SQL Developer release. When you start SQL Developer Release 1.5, click Yes when asked if you want to migrate settings from a previous release. In the dialog box that is displayed, do not accept the default location for the settings.
Instead, specify the location of your settings for the previous release, which might be a folder whose path ends with sqldeveloper sqldeveloper system or Documents and Settings Application Data SQL Developer system. 1.4 Migrating Information from Previous Releases If you have used a previous release of SQL Developer, you may want to preserve database connections that you have been using. To preserve database connections, save your existing database connections in an XML file. To save the connections, right-click the Connections node in the Connections Navigator and select Export Connections. After you complete the installation described in this guide, you can use those connections by right-clicking the Connections node in the Connections Navigator and selecting Import Connections If you want to use any user-defined reports or the SQL history from a previous version, see for information about where these are located. If you have user-defined reports and SQL history from Release 1.0, they are modified by any later SQL Developer release to a format that is different from and incompatible with Release 1.0. SQL Developer preferences (specified by clicking Tools and then Preferences) from a pre-release version of the current release cannot currently be saved and reused; you must re-specify any desired preferences.
1.5 Location of User-Related Information SQL Developer stores user-related information in several places, with the specific location depending on the operating system and certain environment specifications. User-related information includes user-defined reports, user-defined snippets, SQL Worksheet history, code templates, and SQL Developer user preferences.
In most cases, your user-related information is stored outside the SQL Developer installation directory hierarchy, so that it is preserved if you delete that directory and install a new version. The user-related information is stored in or under the following location:. On Windows systems: the HOME environment variable location, if defined; otherwise the SQLDEVELOPERUSERDIR location, if defined; otherwise as indicated in the following table.
On Linux and Mac OS X systems: the SQLDEVELOPERUSERDIR location, if defined; otherwise as indicated in the following table The following table shows the typical default locations (under a directory or in a file) for specific types of resources on different operating systems. (Note the period in the name of any directory named.sqldeveloper.). Table 1-6 Non-Oracle (Third-Party) Database Certification for SQL Developer Database Releases Notes Microsoft Access Access 97 Access 2000 Access XP (2002) Access 2003 For any Access release: no JDBC driver needed, but you must ensure read access to system tables in the.mdb file. Microsoft SQL Server SQL Server 7 SQL Server 2000 SQL Server 2005 For any Microsoft SQL Server release: JDBC driver jtds-1.2.jar required; included in jtds-1.2-dist.zip available from sourceforge.net; also available through Help, Check for Updates. MySQL MySQL 3.x MySQL 4.x MySQL 5.x For any MySQL release: JDBC driver required.
For MySQL 5.x: mysql-connector-java-5.0.4-bin.jar, which is included in mysql-connector-java-5.0.4.zip; also available through Help, Check for Updates. (Do not use the latest MySQL driver 5.1.) Sybase Adaptive Server Sybase 12 Sybase 15 For any Sybase Adaptive Server release: JDBC driver jtds-1.2.jar required; included in jtds-1.2-dist.zip available from sourceforge.net; also available through Help, Check for Updates. For information about creating and using connections to third-party databases, see the information about database connections in the SQL Developer online help or Oracle Database SQL Developer User's Guide. 1.7 Advanced Security for JDBC Connection to the Database You are encouraged to use Oracle Advanced Security to secure a JDBC connection to the database.
Both the JDBC OCI and the JDBC Thin drivers support at least some of the Oracle Advanced Security features. If you are using the OCI driver, you can set relevant parameters in the same way that you would in any Oracle client setting.
The JDBC Thin driver supports the Oracle Advanced Security features through a set of Java classes included with the JDBC classes in a Java Archive (JAR) file and supports security parameter settings through Java properties objects. 1.9 Using a Screen Reader and Java Access Bridge with SQL Developer To make the best use of our accessibility features, Oracle Corporation recommends the following minimum technology stack:. Windows 2000 or Windows XP. Java Sun J2SE 1.5.005.
Sun Java Access Bridge 1.1 or higher. JAWS 3.70.87, or 5.10 or higher Follow these steps to set up a screen reader and Java Access Bridge. If you are using JAWS 3.70.87, see the additional configuration information provided after the procedure. Install the screen reader, if it is not already installed. (See the documentation for your screen reader for more information about installation.).
Install SQL Developer. Download Java Access Bridge for Windows version 1.1. The file you will download is accessbridge-11.zip. It is available from. (See the Java Access Bridge documentation available from this Web site for more information about installation and the Java Access Bridge.).
After downloading the file, extract (unzip) the contents to a folder, for example, accessbridgehome. Install Java Access Bridge by running Install.exe from the installer folder. The installer first checks the SDK version for compatibility, then the Available Java virtual machines dialog displays. Click Search disks.
Then select to search only the drive that contains the SQL Developer build and the SDK version in the program files directory (if it exists). The search process can take a long time on a large disk with many instances of SDK or SQL Developer, or when searching multiple disks. However, unless you complete an exhaustive search of your disk, Access Bridge will not be optimally configured, and will not be correctly installed to all of the Java VMs on your system. After selecting the disk to search, click Search. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog, by clicking Install in All.
Oracle Sql Developer Alternatives For Mac Pro
Click OK when you see the Installation Completed message. Confirm that the following files have been installed in the Winnt System32 directory (or the equivalent Windows 2000 or XP directory), or copy them from installer installerFiles because they must be in the system path in order to work with SQL Developer: JavaAccessBridge.dll JAWTAccessBridge.dll WindowsAccessBridge.dll Note that the system directory is required in the PATH system variable. Confirm that the following files have been installed in the jdk jre lib ext directory, or copy them from installer installerFiles: access-bridge.jar jaccess-13.jar jaccess-14.jar JavaAccessBridge.dll JAWTAccessBridge.dll WindowsAccessBridge.dll. Confirm that the file accessibility.properties has been installed in the jdk jre lib ext directory, or copy it from installer installerFiles. Confirm that the file accessibility.properties includes the following lines: assistivetechnologies=com.sun.java.accessibility.AccessBridge AWT.EventQueueClass=com.sun.java.accessibility.util.EventQueueMonitor AWT.assistivetechnologies=com.sun.java.accessibility.AccessBridge. Only if you are using JAWS version 3.7, do the following: modify the file sqldeveloper.conf located in the folder sqldeveloper bin to uncomment the AddVMOption line, as shown in the following: # # Prepend patches to the bootclasspath. Currently, rtpatch.jar contains a # patch that fixes the javax.swing.JTree accessibility problems.
# Uncomment the line below if you need to run SQL DeveloperSQL Developer under JAWS. # AddVMOption -Xbootclasspath/p././jdk/jre/lib/patches/rtpatch.jar. Start your screen reader.
Start SQL Developer. These steps assume you are running Windows and using a Windows-based screen reader. A console window that contains error information (if any) will open first and then the main SQL Developer window will appear, once SQL Developer has started. Any messages that appear will not affect the functionality of SQL Developer.
1.9.1 Configuring JAWS 3.70 and Access Bridge with SQL Developer The following combinations of Access Bridge file versions are necessary to achieve optimal functionality with JAWS 3.70, since this version of the screen reader uses older Java technology than is used in SQL Developer. There are two stacks of software technology listed below for those who want to use either version 1.0.3 or 1.0.4 of the Access Bridge. Also required in the system32 directory is a copy of the latest version of the Access Bridge jar file. Access Bridge v. 1.10 Uninstalling SQL Developer Before you uninstall SQL Developer, if you plan to install SQL Developer (the same or an updated version) later, you may want to save your existing database connections; and if so, see before uninstalling. To uninstall SQL Developer, remove the entire SQL Developer installation directory (that is, the directory named sqldeveloper and all directories and files under it in the hierarchy).
If you also want to remove all user-specific SQL Developer information, you should also delete the directory under which that information is stored (that is, the SQL Developer user information directory). For the location of this directory, see. If you have created a shortcut for SQL Developer, and if you do not plan to install SQL Developer into the same location again, you should remove that shortcut or modify the shortcut properties to reflect the new location.
1.11 SQL Developer Documentation SQL Developer provides user documentation in the Oracle Database SQL Developer User's Guide and in the online help. To see the help, click the Help menu, or click the Help button or press the F1 key in relevant contexts while you are using SQL Developer. In addition to the user's guide and installation guide, the following migration-related guides are available:. Oracle Database SQL Developer Supplementary Information for Microsoft Access Migrations. Oracle Database SQL Developer Supplementary Information for MySQL Migrations.
Oracle Sql Developer Alternatives For Mac Download
Oracle Database SQL Developer Supplementary Information for Microsoft SQL Server and Sybase Adaptive Server Migrations.
DbVisualizer is widely called as one of the leading database development tools available in the IDE market. DbVisualizer is basically a standalone program containing multiple database management tools for the professional developers and programmers. The best about DbVisualizer is that its database management system is widely available for the almost all type of the databases either it is SQL Server, Oracle, Sybase, MySQL, SQLite or any other.
DbVisualizer is widely available for all leading operating systems such as Mac OS X, Windows, Linux and few others. This universal database developer and management program is called to be one of the best database management solutions for the management of all type of databases.
The main highlighted features and functions of the DbVisualizer are comprehensive database and operating system support, availability of SQL tools, database browsing system, database object management system, table data management system and exporting the objects and tables of databases as well. DbVisualizer features an enormous amount of visual tools that assist the database developers in managing the all of the database objects. DbVisualizer is now offering the database browser with the usage of which the multiple objects can be displayed side by side.
Oracle Sql Developer Tool
DbVisualizer simply improve the database integration for all supported databases. The latest version of DbVisualizer is packed with several support portal for the developers as well.