chapter 3 Flashcards
How static embedded sql works?
static sql queries are embedded in the programming language, which is extended using prefix for SQL operations.
Preconversor/Precompiler converts SQL into function calls of the programming language.
Advantages: Potentially performance
How dynamic embedded SQL works?
SQL queries are treated dynamically by the program. Preprocessor is still required.
How Call-level Interface (CLI) works?
It has the same capabilities as dynamic embedded SQL. SQL queries are string parameters of function invocations.
Requirement for db-gw:
Remote data access, multiple simultanously active DB-connections within the same applicatoin thread, simultaneous acces to multiple DBMS
ODBC x JDBC
In the db gateway architecture, which is the role of the driver manager?
the driver manager is the responsible for manages interactions between applications and drivers, realizes (n:m)relationship between applications and drivers. It load/unload driver, mapping data sources to drivers, communicatation/ logginf of function/ method calls, and simple error handling.
explain ODBC driver type: Single-Tier driver
Data resides on the same machine as the driver. As functionality it completes SQL processing (parse, optimize and execution) and often lacks multi-use and transaction support
explain ODBC driver type: two-tier driver
Driver acts as a client interacting with DBMS (server) through data protocol
explain ODBC driver type: three-tier driver
Middleware server
*gw server
*connects and relays requests to one or more DBMS servers
moves the complexity from the client to the middleware server
*client requires only a single driver for the middleware server
Which are the JDBC driver types?
- type1: jdbc-odbc bridge with 2-tier.
- type 2: native-API partial-java driver, it is also 2-tier
- type3: net-protocol ALL-JAVA driver. It is 3-tier and does not requeire natie binaries on client
- type 4: native-protocol all-java driver. It is 2-tier and pure java. It implements the network data protocol of the DBMS
WHY is SQL/OLB (SQLJ part0) a big problem to large enterprise?
Because in SQL/OLB there is no notion of „program“ per say. End users must have table privileges, and it is not easy to solve in a large enterprise.
SQLJ
Combines advantages of embedded SQL with binary portability