1. BR SQL SUPPORT I have a legacy application and I don’t intend to rewrite it any time soon. Why should I be concerned with this?

2. RELEVANCE Data Conversion for New Customers Programmed access to Excel spreadsheets Abstract IO will enable legacy applications to store data outside of BR. Native SQL support Performance considerations

3. Abstract IO We will describe Abstract IO in detail tomorrow. The actual concept will be described in brief at the end of this presentation. For now, regard it as a facility that will enable SQL to emulate BR file processing – with no change to your programs. Support for SQL is only one of several possible applications of the Abtract IO concept.

4. DATABASE NOMENCLATURE Database == Group of Files Table == One File Row == One Record Column == One Field

5. BR SQL STRUCTURE Database identified in Configuration statements. More than one connection is allowed. OPEN statement specifies the SQL. Only one OPEN per connection at a time. WRITE executes the SQL. READ reads a row of the SQL results.

6. BR SQL EXAMPLE PROGRAMS CONNECT – Get a connection string ENVDB – Print a table layout EXTRACT – Print the values in a table UPDATE – Update a few fields COPY – Copy from one table to another

7. NEW STATUS ENV FILTER STATUS ENV can produce voluminous output ENV$(“STATUS”) can filter based on keywords Now ST ENV can also filter based on keywords Enclose all keywords in a single quoted string Comma separate multiple keywords Use tilde ( ~ ) to negate http://brwiki2.brulescorp.com/index.php?title=Status#Status_Env

8. Working With Databases MySQL SQL Server Excel Firebird