Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home
Jazz home  >  Papers & Training

IMAGE/SQL: Issues and answers concerning SQL tables

» 

Jazz home

»

Software

»

Papers & Training

»

Java

»

HP Partners

»

News & Events

»

Register for more info

Content starts here
Prev Page Next Page Manual Top Home Page


1.4 What SQL terminology should I know?



Key points


  • The concept of a database in TurboIMAGE maps to two different concepts in IMAGE/SQL and ALLBASE/SQL:

    1. A DBEnvironment (or DBE) is primarily a set of SQL tables that share the same system catalog and the same logging and recovery. Typically you store and restore all files in the DBE at the same time.

    2. In SQL terminology, a database is a set of SQL tables within a particular DBEnvironment that share the same owner. When a table is created, both an owner and a tablename are assigned to completely identify it. Since it is possible to create tables having different owners within a single DBE, multiple databases can exist within a DBE.

    IMAGE/SQL allows you to attach several TurboIMAGE databases to a single DBEnvironment. The data sets are registered as tables in the system catalog; all data sets from the same TurboIMAGE database have the same owner. So, each TurboIMAGE database is also a unique "database" in SQL terminology.

  • An SQL table is similar to a TurboIMAGE data set.

  • An SQL row has one or more columns.

  • You can create hash indexes, B-tree indexes or parent-child relationships (referential constraints) on SQL tables.

  • In SQL, security is primarily based on the end-user's logon id, not on a password. The DBA grants and revokes database priviledges to a particular logon id. The DBA can also define a group, and grant/revoke to the group in the same way as to a particular logon id. Each logon id added to the group has the same priviledges as the group. Finally, the DBA can add groups to other groups.

  • In TurboIMAGE, several types of transactions are defined. A dynamic transaction is a logical transaction which has the following attributes:

    • It begins with a DBXBEGIN call and normally ends with a DBXEND call; it can be rolled back dynamically with a DBXUNDO call.

    • It spans only one database. A program can open more than one database if it needs to access data sets from different databases, and can have dynamic transactions in effect on different databases at the same time.

    In DBCORE, only one type of transaction is defined. A DBCORE transaction is essentially equivalant to a TurboIMAGE dynamic transaction, and has the following attributes:

    • It begins with a BEGIN WORK statement and normally ends with a COMMIT WORK statement; it can be rolled back dynamically with a ROLLBACK WORK statement.

    • It spans only one database. A program that needs to access tables in more than one DBEnvironment can do so by connecting to multiple DBEnvironments; however, only one connection can have an active transaction at any time (it is not possible to reference tables from multiple DBEnvironments within a single transaction). A program must end a transaction on one DBEnvironment before starting a transaction on a second DBEnvironment.

      Most interactive Client/Server tools only allow you to connect to a single DBEnvironment at a time.


    Prev Page Next Page Manual Top Home Page

    Page last updated on November 29, 1995

  • Printable version
    Privacy statement Using this site means you accept its terms Feedback to webmaster
    © 2004 Hewlett-Packard Development Company, L.P.