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.1 What subjects are covered in this presentation?



Key points


If you are a TurboIMAGE programmer, you are already familiar with the key concepts needed to develop an application that calls TurboIMAGE intrinsics. The goal of this tutorial is to make you familiar with similar concepts for the SQL part of IMAGE/SQL, so that you have the ability to develop an SQL application that accesses information stored in either TurboIMAGE data sets or SQL tables.

I'll go out on a limb here, but I'm willing to bet you did not learn everything that you needed to know about TurboIMAGE from a two-hour tutorial. When I was involved with IMAGE programming, I took several multi-day customer courses to come up to speed.

SQL is complex. Where does one start? This tutorial will try to give you a jump-start into the world of SQL. My objective is to expose you to key SQL concepts, and to show you where to go for additional information. The illustration on the diagram is supposed to be similar to an iceberg. We'll cover the 'tip' of the iceberg in this class, but not the entire iceberg.

When you jump-start your car, an intense burst of energy passes into the battery. In this tutorial you will be exposed to much information. I recommend that you first try to focus on the "big picture" instead of all of the details. You can always come back again later.

Major topics to be covered:

  • Chapter 1 - Overview
    • How are TurboIMAGE/XL, ALLBASE/SQL, and IMAGE/SQL related?
    • Why should I care about SQL tables?
    • What SQL terminology should I know?
    • Where can I get additional information?

  • Chapter 2 - SQL Storage
    • Review physical storage for TurboIMAGE.
    • How are SQL tables physically stored?
    • How does the optimizer locate rows?

  • Chapter 3 - SQL Security
    • What are the key elements of SQL security?
    • How does IMAGESQL.PUB.SYS implement SQL security?

  • Chapter 4 - Trouble-Shooting with SQLMON
    • What is it?
    • Where is it?
    • How do I use it?

  • Chapter 5 - SQL Transactions and Locking
    • SQL Transactions (starting, ending, timeouts, etc.)
    • How are deadlocks resolved by ALLBASE/SQL?
    • SQL DBECon file parameters associated with locking.
    • How does the SQL optimizer affect locking?
    • What is an SQL cursor?
    • And everything else you ever wanted to know about SQL locking!

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.