Oracle Tools

Database application development is usually divided into two stages: database design and application writing. Oracle Data Access Components for Delphi (ODAC) allow implementation of work with Oracle server, and dbForge Studio for Oracle – database design and administration. Now, for convenient development, integration with dbForge Studio for Oracle is implemented in ODAC.

To enable integration to dbForge Studio for Oracle, in the Delphi main menu select ODAC → Database Tools → dbForge Studio for Oracle Integration.

(more…)

Some of our users have faced the situation when they need to change the connection details of the existing Database Diagram file.

Let’s assume the situation when you have several databases with identical schemas which are only located on different MySQL servers and you have created a database model that was saved in a Database Diagram file. Now, you want to avoid redesigning the database model from scratch and only reassign the existing database model to another MySQL server. (more…)

We’ve analysed user feedbacks received after the release of the completely redesigned dbForge Studio and defined prior points for further development of the product.

As a result we’ve devoted the new release of dbForge Studio for Oracle to improving the possibilities for users who work with PL/SQL code and data. And in addition we’ve improved the application performance and added support for Win-x64 platform. (more…)

When developing databases, we frequently need to check what changes were made to its schema, if any mistakes were made, and, if there are any, we should roll back to the working version saved in the source control system. To do this, it’s enough to compare schemas of version 1.1 and 1.2, and generate an UPDATE SCRIPT using any Database Diff tool, including our dbForge Schema Compare for Oracle.

So what functionality should be available in such tool?

Firstly, the tool should be easy-to-use and user-friendly. A user should not be obliged to learn a pile of topics in the tool documentation before using it. It should be enough to perform the following set of steps:
1) Select Source and Target
2) Select a schema or several schemas (if the tool provides such possibility) for comparison
3) Tune comparison process by checking the needed options (an optional step)
4) View comparison results
5) Tune script generation options (an optional step)
6) Generate an update script and/or execute it directly to the target database
Secondly, the tool should support comparison of all object types you might have in your schemas – otherwise, how the tool is supposed to look for differences in them? And, at last, the tool should be fast. This point is especially important for searching data differences, when comparison of several schemas is performed, or the size of the project itself is large.

Now let’s look at Oracle SQL Developer and its alternative — dbForge Schema Compare for Oracle. Both are offering schema comparison functionality.
(more…)

This article is a step-by-step instruction for configuring Oracle Instant Client so that our tools for Oracle could work with it.

(more…)

Having successfully released our data comparison tool for Oracle we went further by starting the new one. dbForge Schema compare for Oracle is targeted to help database developers perform sustainable change management process. The tool is designed to:

• compare Oracle schemes
• analyse changes between databases
• generate schema comparison reports
• synchronize databases immediately or save sync scripts for later use

In order to allow our users make changes and improve product even before the first release we decided to publish early access preview of the dbForge Schema Compare for Oracle.

Visit product page http://www.devart.com/dbforge/oracle/schemacompare/ download product and leave us a feedback.

Recently we were working over the release of the version 2.0 of  dbForge Data Compare for Oracle. One of the main features added to the new version was synchronization of the LOB data. When we developed the first release of the product we postponed this feature because of challenges of synchronizing LOB data. These challenges caused by nature of data stored in BLOB or CLOB columns. It’s large and simply does not fit into SQL script. But we’ve found the solution.

In this article we will examine basic methods of loading LOB data into a table.

(more…)

During replicating data in one or another way, it happens that synchronized objects may differ. This situation may take place in the following cases:

• If changes made in one of copied databases were not captured
• The changes were captured but not forwarded
• The changed were forwarded but not applied due to some reasons

It should be admitted that full or partial synchronization may be required due to some other reasons, not related to replication. But the question is how to synchronize database objects?
(more…)

In the process of developing databases many developers and testers encounter a problem of synchronizing data between local and remote Oracle database. Changes made in a local database must be reflected in a remote database. It’s also necessary to check test results with the model database, to find non-synchronized tables that appeared after these tests, to have possibility to return the test database to its initial state when testing newly developed versions of databases intensively. Another problem may be to create CRUD operations quickly without making too much effort to find different objects and to write DML statements. Now let’s find out how one can synchronize data of Oracle databases.

Simple solutions:
(more…)

When you perform data maintenance operations, sometimes, it’s necessary to disable or enable all foreign keys in the user schema.

Here is the script that solves this task:
(more…)