8_2

OpenEdge® SQL in a 10.1B multi-database environment for ODBC and JDBC

Doug MerrettSenior Solution Engineer – EMEA

Progress Software

© 2007 Progress Software Corporation2 OpenEdge SQL multi-database environment for ODBC and JDBC

Objectives

Answers for the following:

What is multi-database query?

What’s going on under the covers?

How do I manage the configuration?


Agenda

Overview of multi-database configurations

Connections and how they show up

Data access – single and multi-database

Management and planning


Multi-Database Query – Done on Client

DB

SQL Client

Second DB

ThirdDB

DBNavigator – JDBC URL

Crystal Reports – ODBC DSN

Allow the ability to join tables in multiple databases (cross database join)

CustomersOrders Inventory

Join: customers from DB, Orders from SecondDB, Inventory from ThirdDB


10.1B Multi-Database Query – Done on Server

OpenEdge SQLServer

DB

SQL Client

Host

Shmem

Second DB

Third DB

Shmem


Shmem


Cross database join


Fields/Columns (CustNum, CustName)

Table (Customer) - collection of columns

Schema (PUB, dmerrett) - collection of tables

Catalog (AuxCat1, mysports) - Alias for database

Terminology


Multi-Database Query – Scope

PUB schema PUB

Customer Inventory

dmerrett

Mysports AuxCat1


Three level naming convention

Example

Applies to schema, tables, columns, stored procedures

3 part naming – single database connection

Three level naming (already have this)

schema.table.column-name

SELECT Pub.Customer.CustNum, Pub.Customer.Name, Pub.Order.OrderNum ...


Four level naming convention

Example

Applies to schema, tables, columns, stored procedures

4 part naming – multi-database query

Four level naming

catalog.schema.table.column-name

SELECT Pub.Customer.CustNum, SportsPrimary.Pub.Customer.Name, SportsAux1.Pub.Order.OrderNum ...


SELECT "Customer1"."CustNum", "Customer1"."Name", "Order1"."OrderDate", "Order1"."Ordernum", "OrderLine1"."Itemnum", "OrderLine1"."Qty", "OrderLine1"."OrderLineStatus"

FROM ("AuxCat2"."PUB"."OrderLine" "OrderLine1" INNER JOIN "AuxCat1"."PUB"."Order" "Order1" ON "OrderLine1"."Ordernum"="Order1"."Ordernum") INNER JOIN "SPORTS2000"."PUB"."Customer" "Customer1" ON "Order1"."CustNum"="Customer1"."CustNum"

ORDER BY "Customer1"."CustNum"

Crystal Reports – cross database join

Catalog


Single Database

Simple query

OpenEdge SQLServer

DB

SQL Client

Host

Shmem




Multi-Database Support

DB

Primary

SQL Client

Host

Shmem

Auxiliaries

Second DB

Third DB

Read Only

Shmem

Shmem



OpenEdge SQLServer

Define primary and auxiliary database


Agenda






Multi-database connections

Two methods:

Explicit connections to auxiliary databases with CONNECT sql statement

“Automatic” connection model


Connecting to an Auxiliary Database

Catalog – an alias for a database

Connecting to an auxiliary database

• Must be on same host as Primary database

Disconnecting a catalog

CONNECT ‘/usr/wrk/sports2000’ AS CATALOG mysports;

DISCONNECT CATALOG mysports;


Auxiliary Database Details

Default catalog is the Primary database

Listing available, currently connected catalogs

Syntax

SET CATALOG mysports;

SHOW CATALOGS ALL | { PRO_NAME | PRO_TYPE | PRO_STATUS }


Say What ?!?!

Some applications, like Crystal Reports, only allow you to issue SELECT statements

Can’t use the CONNECT statement:

Now what?

Use automatic connections


Multi-Database : automatic connections

Properties[config]

OpenEdge SQLServer

dbname[-mdbq:config]

DB

Primary

SQL Client

Host

Shmem

Auxiliaries

Second DB

Third DB

Read Only

Shmem

Shmem




Automatic connections

How does solution this work? What is a property file? What does the property file contain?


Property file example

[sql-configuration] configuration-names-list=config1[configuration.config1] database-id-list=Aux1, Aux2[database.Aux1] Name=SportsAux1 Catalog=AuxCat1 Location=c:\openedge\WRK\db\SportsAux1[database.Aux2] Name=SportsAux2 Catalog=AuxCat2 Location=c:\openedge\WRK\db\SportsAux2

sports2000.oesql.properties

Full path to database

configuration name


Multi-Database : automatic connections

Properties[config1]

OpenEdge SQLServer

dbname[-mdbq:config1]

DB

Primary

SQL Client

Host

Shmem

Auxiliaries

Second DB

Third DB

Read Only

Shmem

Shmem




Single DB connection : JDBC – DBNavigator

jdbc:datadirect:openedge://localhost:6748;databaseName=sports2000


Multi DB connection : JDBC – DBNavigator

[-mdbq:config1]jdbc:datadirect:openedge://localhost:6748;databaseName=sports2000


DBNavigator – MDBQ configuration

Primary database

Auxiliary databases


ODBC – Single DB configuration


ODBC – Multi DB configuration


Crystal – looks like this with MDBQ

Auxiliary databases

Primary database


Every good engineering project has acronyms (EGEPHA)

Primary or single database connections SQSV (OpenEdge SQL Server)

• Main OpenEdge SQL server process connection to storage engine

REMC (Remote Client) • OpenEdge SQL client thread for each

connection to the primary database


Under the covers - acronyms

Auxiliary connections SQFA (SQL Federated Agent)

• Main OpenEdge SQL connection to the Auxiliary database

SQFC (SQL Federated Client)• OpenEdge SQL client thread for each

connection to the auxiliary database


Connection types

OpenEdge SQL Server connection

OpenEdge SQL Client connection

Primary SQSV REMC

Auxiliary SQFA SQFC


Connections – using MDBQOpenEdge SQL Server

Primary DB

Auxiliary DB

Main Thread

Client 1 Thread

Client 2 Thread

SQSV

SQFA

REMC

REMC

SQFC

SQFC


Promon – Primary Database

Primary database connections


Promon – Auxiliary Database

Auxiliary database connections


OpenEdge Management User Activity View – Primary DatabasePrimary database connections


OpenEdge Management User Activity View – Auxiliary DatabaseAuxiliary database connections


MDBQ Tips/Restrictions/Gotchas!!

Restriction • Primary and auxiliary databases must reside

on same host Connection authentication

• User credentials must be same on Primary and each Auxiliary

Database codepage• Codepage of databases must be the same


MDBQ Tips/Restrictions/Gotchas!!

Auxiliary connections are READ ONLY• No update operations, schema or record based,

can be performed in the auxiliary databases.Only the primary database will accept update statements.

Granting / revoking permissions – authorization• Must be done on auxiliary database independently

Performance considerations• Update Statistics must be done on each auxiliary

database independently


Multi-Database Query Support

Properties[config1]

OpenEdge SQLServer

dbname[-mdbq:config1]

DB

Primary

SQL Client

Host

Shmem

Auxiliaries

Second DB

Third DB

Shmem

Shmem

Read Only






Agenda


Planning – startup

Effect of MDBQ: Primary DB startup parameters• Effectively no change from single connection,

make use of –Mi to control number of connections/threads per server. Still have SQSV (server slot (-Mi,Ma)) and REMC (user slot (-n))

• Reminder: OpenEdge SQL does better with threads (more connections per server)

Effect of MDBQ: Auxiliary DB startup parameters• SQFA is self-service (add one to –n) • Each SQFC takes up a user slot (each add to –n)• SQFA, for each SQSV, will host multiple SQFC

contexts


Shutdown of Auxiliary databaseOpenEdge SQL Server

Primary DB

Auxiliary DB

Main Thread

SQSV

SQFA

Client 1 Thread

REMC

SQFC

Client 2 Thread

REMC

SQFC

Primary DB broker unaffected


Shutdown of Auxiliary database

Primary DB

Auxiliary DB

Main Thread

SQSV

Primary DB broker unaffected

OpenEdge SQL Server


Shutdown of Primary database

Primary DB

Auxiliary DB

Main Thread

SQSV

SQFA

Client 1 Thread

REMC

SQFC

Client 2 Thread

REMC

SQFC

OpenEdge SQL Server

Auxiliary DB broker unaffected


Shutdown of Primary database

Primary DB

Auxiliary DB

Auxiliary DB broker unaffected


Promon – Disconnect of SQFA

Primary DB

Auxiliary DB

Main Thread

SQSV

SQFA

Client 1 Thread

REMC

SQFC

Client 2 Thread

REMC

SQFC

OpenEdge SQL Server

Primary and Auxiliary DB broker unaffected


Promon – Disconnect of SQFA

Primary DB

Auxiliary DB

Main Thread

SQSV

OpenEdge SQL Server



Promon – Disconnect of REMC or SQFC

Primary DB

Auxiliary DB

Main Thread

SQSV

SQFA

Client 1 Thread

REMC

SQFC

Client 2 Thread

REMC

SQFC

OpenEdge SQL Server



Promon – Disconnect of REMC or SQFC

Primary DB

Auxiliary DB

Main Thread

SQSV

SQFA

Client 1 Thread

REMC

SQFC

OpenEdge SQL Server



In Summary

Multi-database query

Manage the configuration

Under the covers


For More Information, go to…

PSDN

Progress eLearning Community• Using OpenEdge SQL

Documentation – 10.1B• OpenEdge Data Management: SQL Development• OpenEdge Data Management: SQL Reference


Relevant Exchange 2007 Sessions

DB-10: What’s New in OpenEdge 10.1B RDBMS

DB-11: Moving to OpenEdge COMP-10: OpenEdge Management and

Replication DB-21: Data Management Roadmap and

Info Exchange


Questions?


Thank you foryour time


Date post:	21-Nov-2014
Category:	Documents
Upload:	123okman
View:	36 times
Download:	2 times

8_2

Documents