Designing & Engineering Oracle Databases
Introduction
Oracle Database is the first database designed
specifically for the internet Visual case provides full
support for the most used features of versions 8 and 9. Visual Case also facilitates
the migration from older versions.
Using
Visual Case to Design Oracle Databases
A database
can be built in Visual Case using the design tools or by reverse
engineering an existing database. If a design already
exists for a database of a different type it can be converted to
Oracle.
For an
introduction to database design, visit our database design
tutorial.
Columns These are built in
the table property page. Select a standard or user defined data
type from the list.
Data-types Visual
Case supports all the standard data types.
Custom Data-types User
defined data types can be defined from the database property page.
The database engineer does not forward engineer custom types. They must be created in the
physical database using Oracle utilities before running the forward
engineer. The reverse
engineer will process columns in a physical database using custom
data-types. Visual case
will prompt the user and can either substitute a standard data type
for the dictionary entry or create a user-defined data-type in the
Visual Case dictionary.
Sequences (New in 2.6)
Sequences are supported and can be created and
maintained on the database property page.
Constraints Maintain
these on the table property page.
Indexes These are
fully supported including primary, unique and ascending or
descending.
Foreign Keys These are supported
with restrict, set null, default or cascade on delete. On update can restrict or
cascade. Setting the child cardinality will synchronize the "allow
null" option on the foreign key columns and create a unique index if
the cardinality is "one only".
Triggers These are
fully supported and are easy to design using our SQL
editor.
Stored Procedures and
Views These are defined in the
database property page. Undock the editor to edit a long procedure or
view.
SQL Editor
This editor is automatically activated for editing script and is
aware of the standard language features and names of dictionary
objects.
Engineering Oracle Databases
Visual Case's database engineering wizard
will forward and reverse engineer all database attributes that
can be defined in your Visual Case design of an Oracle database with
the exception of custom data-types that must be manually created in the physical database
before running the forward engineer.
The
wizard allows you to compare the differences between your database
design and the physical database before completing either the
forward or the reverse engineer.
The
forward engineer builds a SQL script that can be saved and
manually run at a later time.
You
can quickly forward-engineer a single entity (table, stored
procedure, etc.) from its right-click menu or from its property
page.
For
more information about forward and reverse-engineering databases,
please visit our database engineering
tutorial.
Migrating to Oracle
Visual Case will convert any supported database type to Oracle
and migrate between Oracle versions. Visual Case will
also reverse engineer most ODBC or JDBC data sources to Oracle, even
if the physical database is not a type directly
supported.
Because
of differences between database data types conversion is usually a
one-way process. For
example, converting a SQL Server varchar(300) column to Access will
produce a column of type memo as Accesss text data type is limited
to 255 characters. Converting back to SQL Server will produce a column of type
text as a memo column can be quite long!
Free Trial Download
Finally, download the 30 day free trial of
Visual Case and get started.
Visual CaseTM is a trademark or
registered trademark of Artiso Corp. Canada.
Microsoft,
Windows, SQL Server, VB, Visual Basic and Access are registered
trademarks of Microsoft Corporation. Oracle is a registered
trademark of Oracle Corporation. Unified Modeling Language and
UML are trademarks of Object Management Group Inc. in the U.S. and
other countries. Other brands and their products are trademarks
or registered trademarks of their respective holders and should be
noted as such.
This site is best viewed at a resolution of 800 by
600 using Internet Explorer 5.
|