EnterpriseDB Configuration Mode
Oracle Tips by Burleson Consulting
2.3: Configuration Mode
The Redwood mode
sets some configuration options to make EnterpriseDB behave more like Oracle.
For example, the default date format will be the Redwood style, DD-MON-YYYY.
The sample application that is installed will also be Redwoodish.
mode sets the configuration options to be more like a standard install of
Either way, you
still have full compatibility with both PostgreSQL and Oracle. I chose Redwood
and the databases we will be using for the remainder of this book will have been
installed in Redwood mode.
If you are going
to follow along with the examples in this book, I would recommend that you also
install your database in Redwood mode. I will discuss the options that
differentiate the Redwood and PostgreSQL modes later but your queries may not
look like the example queries if you choose PostgreSQL now.
EnterpriseDB destination screen (Figure 2.4), you can select where you would
like to install the EnterpriseDB executables. You will have a chance later in
the installation process to choose where you would like to install your data
Executables Destination Path
Unless you have a
specific need to control the installation directories, I would recommend
accepting the defaults. I will be referring to directories later in the book
and it will be easier to keep up if your installation matches mine.
The next screen,
Figure 2.5, is a list of the features you would like to install. As with the
destination path, I recommend that you also accept the default options on this
screen. You don’t need to use them if you don’t want to but at least they will
be installed should you need them.
You can install
the database without the EnterpriseDB Network. If you do, you will miss out on
many of the enterprise-class tools that are provided with the database and you
will not be able to follow along in many areas of this book. For the rest of
the book, I am going to assume that you have installed the EnterpriseDB Network
The first two
options in Figure 2.5 are the Database Server (which are the database binaries)
and Developer Studio (which is the tool for browsing and developing in
The next option
allows you to choose your client connectors. EnterpriseDB currently ships with
drivers for ODBC (open database connectivity), .Net (MS and Mono CLRs) and JDBC
(Java). We will only be using the JDBC connector in this book. However, the
connectors for EnterpriseDB work just as they would for Oracle or any other
The next option is
for Spatial Extensions. Spatial Extensions add geographic objects to the
Database Server to support geographic information systems.
The final option
is the EnterpriseDB Network. If you select this, you will be able to install
the Remote DBA Management Server (which you definitely want), the migration tools
(which you need if you are migrating an Oracle database) and the debugger (which
is useful when you are developing applications). You also get searchable
documentation in PDF format.
Accept the default
and hit next.
To continue, you
will need to choose an online or offline installation, Figure 2.6.
This is an excerpt
from the book "EnterpriseDB: The Definitive Reference" by Rampant TechPress.