There are a variety of reasons to use SQL Data Definition Language (DDL) rather than Data Definition Specifications (DDS) to define your iSeries database files (or tables and views, as they're known in SQL terminology). Many SQL functions aren't available in DDS (e.g., views with summary values), and SQL is both IBM's and the industry's standard database language. But there's another important reason � performance. For many situations, access is faster for files defined with SQL DDL than with DDS.
To understand the performance implications of using SQL versus DDS, it is important to talk about some of the architectural basics, including differences between SQL and DDS. Fundamentally, SQL tables are OS/400 physical files, and SQL views and indexes are OS/400 logical files. As a result, many of the capabilities and behaviors of SQL objects are identical or similar to their OS/400 counterparts. But there are two very important differences: data validation and access path size
Thursday, August 25, 2005
Subscribe to:
Post Comments (Atom)
Popular Posts
- Yahoo! Mail: Revenge of the Oddpost
- MobileTracker - Cingular announces EDGE Wireless WAN service
- Linux Forum: Apache, Webmin and Mandrake - Linux Operating System Help
- Free AS400 & iSeries Software Tools & Utilities Downloads
- Common Gateway Interface (CGI) on the as400 / iSeries
- Table designs based on CSS and DIV elements
- The Laughing Boardroom video...a real world example!
- UDATE and *DATE in AS400 RPG
- IBM eServer iSeries - The Laughing Boardroom
- Does Anybody Care About AIX on the iSeries?
No comments:
Post a Comment