Registering Servers
Once you have installed Aqua Data Studio you
will need to register your servers before you get started. Below is a list of descriptions on how to register a server
according to database type. Sometimes there are issues in connecting to a specific type of database. Each section
offers specific notes for the different database types.
|
Register Oracle Server - If you have any issues connecting to your Oracle
instance, make sure that you can ping your server with 'tnsping'. Also, make sure you have the correct JDBC driver if you are
connecting through OCI libraries. (Drivers)
Aqua Data Studio also allows you to connect to Oracle RAC and Oracle Connection Manager by entering into "Host" value:
Oracle Connection Manager Examples:
(description=(address_list=(address=(protocol=tcp)(port=1610)(host=webHost))
(address=(protocol=tcp)(port=1521)(host=oraHost)))
(connect_data=(INSTANCE_NAME=orcl))(source_route=yes))
Oracle RAC Examples:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521)))
(CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME)))
(DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxx)
(PORT=1526))(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=1526)))
(CONNECT_DATA=(SERVICE_NAME=somesid)))
|
 Oracle Registration
|
| Register DB2 Server - Before connecting to your server, make sure you have
the appropriate driver for your DB2 version and fixpack.
|
 DB2 Registration
|
| Register Informix Server - Informix registrations should be straight forward.
|
 Informix Registration
|
Register Microsoft SQL Server - SQL Server registrations should be straight forward.
Windows Single Sign-On - Aqua Data Studio supports trusted single sign-on connections to SQL Server on the Windows platform.
You may specify the authentication as "Windows Single Sign-On", which will allow ADS to login into a server using the currently
logged in authentication of the OS. This is only supported on the Windows platform, and not on Linux, OSX or other platform. For
other platforms use the "Windows Authentication" option.
Windows Authentication - Aqua Data Studio supports trusted connections to SQL Server on non-Windows platforms. You may
specify the authentication as "Windows Authentication" and specify the Domain/Username and password of the user to authenticate
with.
Connecting to Multiple Instances of SQL Server on the same machine -
When registering an SQL Server you may specify in the Hostname text the name
of the SQL Server and the Instance name in the format \\ServerName\InstanceName
without a port, to enable an Instance connection. You may also connect to multiple
Instances of SQL Server on the same machine
by identifying on what ports each Instance is running. For SQL Server
2000 you can run the "SQL Server Network Utility". You may then select the
Instance of SQL Server and make sure the "TCP/IP" protocol is enabled. Then
you may select the TCP/IP protocol and click properties, this should tell
you the default port.
Once you know the port of each Instance you may register a connection for
each Instance by specifying the hostname and the port for each
connection/instance.
|
 SQL Server Registration
|
| Register PostgreSQL Server - If you have issues connecting to your PostgreSQL
server, make sure that you have started your PostgreSQL postmaster with the '-i' option which enables TCP/IP connections.
TCP/IP connections are required for ADS to connect to the PostgreSQL server.
|
 PostgreSQL Registration
|
| Register MySQL Server - Before connecting to MySQL you will need to GRANT access
to your user and machine. Because the MySQL JDBC driver uses TCP/IP sockets instead of Unix Domain Sockets, the security
manager in MySQL server will use the HOSTS table to determine whether or not the connection should be allowed. To grant
your user access use this syntax: "GRANT ALL PRIVILEGES ON [dbname].* to '[user]'@'[hostname]' identified by '[password]'"
to generate and execute an SQL command.
|
 MySQL Registration
|
| Register Sybase Server - Sybase registrations should be straight forward, although
you should make sure your Sybase server has had the Sybase sql_serverXX.sql meta data script applied to it as documented in
your Sybase documentation. This script is usually applied during installation by default.
|
 Sybase Registration
|
| Register Sybase Anywhere Server - Sybase Anywhere registrations should be straight forward.
|
 Sybase Anywhere Registration
|
| Register Sybase IQ Server - Sybase IQ registrations should be straight forward.
|
Sybase IQ Registration
|
| Register Generic JDBC & ODBC Server - When registering a server using the
Generic-JDBC connection type, make sure you specify the location of the driver which you will be using, with the correct
URL and driver name. When registering a Generic-ODBC connection make sure that an ODBC datasource has already been
created for use.
|
 Generic JDBC Registration
|
|
|
-
Filter Databases/Schemas: Allows the user to specify the main schema browser filter for databases or schemas, on whether to include or exlude all.
-
Include Databases/Schemas: A list of databases/schemas to include after the main filter is applied.
-
Exclude Databases/Schemas: A list of databases/schemas to exclude after the main filter is applied.
-
Filter Objects: Allows the user to specify the main schema browser filter for object types, on whether to include or exlude all.
-
Include Objects: A list of objects to include after the main filter is applied.
-
Exclude Objects: A list of objects to exclude after the main filter is applied.
-
Txn Isolation Level: Support for setting Transaction Isolation Level
- TRANSACTION_NONE - A constant indicating that transactions are not supported.
- TRANSACTION_READ_COMMITTED - A constant indicating that dirty reads are prevented; non-repeatable reads and phantom reads can occur.
- TRANSACTION_READ_UNCOMMITTED - A constant indicating that dirty reads, non-repeatable reads and phantom reads can occur.
- TRANSACTION_REPEATABLE_READ - A constant indicating that dirty reads and non-repeatable reads are prevented; phantom reads can occur.
- TRANSACTION_SERIALIZABLE - A constant indicating that dirty reads, non-repeatable reads and phantom reads are prevented.
-
Driver Param: This option is to allow a user to specify extra JDBC parameters that a user might want use in estabilishing a connection.
-
Charset: Character set used for the connection.
-
Set quoted_identifier: Causes connection to follow the SQL-92 rules regarding quotation mark delimiting identifiers and literal strings.
-
Set ansi_nulls: Causes connection to follow SQL-92 compliant behavior of the Equals (=) and Not Equal to (<>) comparison operators when used with null values.
-
Set ansi_null_dflt_on: Causes connection behavior to override default nullability of new columns when the ANSI null default option for the database is false.
-
Set ansi_padding: Changes connection behavior in the way the column stores values shorter than the defined size of the column, and the way the column stores values that have trailing blanks in char, varchar, binary, and varbinary data.
-
Set ansi_warnings: Specifies SQL-92 standard behavior for several error conditions.
|
