SEQUEL 10 Enhancements

Welcome to SEQUEL 10. Now, SEQUEL offers faster connections to your local System i data and simplifies access to remote databases with its powerful, familiar, easy-to-use functions.

 View Size Expanded for Enhanced Querying

The maximum size of the SQL statement in a SEQUEL view (query) has been expanded from 5,000 to 20,000 characters.

• This new view size helps you create longer and more complex views.
• The expanded size makes it easy to use familiar SEQUEL syntax to create database-specific queries.

Automatic SQL Translation and Faster Queries

SEQUEL 10 can automatically convert SEQUEL SQL to either standard SQL or database-specific SQL. Now, it’s easy to create SEQUEL views for both remote databases (such as SQL Server, Oracle, and MySQL) and the local System i database, using SEQUEL’s easy-to-use syntax and powerful functions—such as CVTDATE and ACCUM—that you’re familiar with.

• The new SYNTAX parameter, which has been added to any SEQUEL command that works with SQL (such as CRTVIEW, DISPLAY, and DSNREPORT), translates SEQUEL SQL at run time for faster execution.

  • For local System i access, SEQUEL converts the SEQUEL SQL to standard SQL.
  • For remote server access (such as MySQL), SEQUEL converts the SEQUEL SQL to SQL that is specific for the server.
     
• SEQUEL 10 queries local System i data faster. When you specify the new *LOCALSYS value on the SERVER parameter, SEQUEL uses a faster SQL query engine (SQE) to access the database on the local System i server.
   
• For easier view creation, SEQUEL SQL statements can use unqualified filenames. Behind the scenes, the *LOCALSYS value helps translate SEQUEL SQL to standard SQL by using the job’s library list.