Data Structures (from Fraktal SAS Programming): Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
K |
K |
||
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
Zeile 1: | Zeile 1: | ||
− | [[Kategorie: | + | [[Kategorie:zazy]] |
+ | {{SeitenNavigation1 | ||
+ | |links=xx_left.png | ||
+ | |zurück=Programming (from Fraktal SAS Programming) | ||
+ | |rechts=xx_right.png | ||
+ | |vorwärts=Preface (from Fraktal SAS Programming) | ||
+ | |hoch=Duck_zazy_com.png | ||
+ | |übersicht=Fraktal SAS Programming | ||
+ | }} | ||
== Why ''"Data Structures"''? == | == Why ''"Data Structures"''? == | ||
Zeile 7: | Zeile 15: | ||
Apart from nowadays well known '''data tables''' and '''data views''', SAS provides the programmer with a '''generalized approach on views''' beyond SQL views as well as '''ultra-fast read-only structures''' for left outer joins and, finally, a '''metadata repository in physical memory (!)''' with support for hierarchical modular programming. | Apart from nowadays well known '''data tables''' and '''data views''', SAS provides the programmer with a '''generalized approach on views''' beyond SQL views as well as '''ultra-fast read-only structures''' for left outer joins and, finally, a '''metadata repository in physical memory (!)''' with support for hierarchical modular programming. | ||
− | * [[Tables and Views (from Fraktal SAS Programming)|Balancing storage demand, processing speed and flexibility at runtime by properly utilizing Tables and Views in SAS and DBMS.]] | + | * [[Tables and Views (from Fraktal SAS Programming)|'''Balancing storage demand, processing speed and flexibility at runtime''' by properly utilizing Tables and Views in SAS and DBMS.]] |
− | * [[Meta Data Tables (from Fraktal SAS Programming)|Structure and organize your runtime information to get a maximum of code from a minimum of programming effort.]] | + | * [[Meta Data Tables (from Fraktal SAS Programming)|'''Structure and organize your runtime control information''' to get a maximum of code from a minimum of programming effort.]] |
− | * [[SAS Formats (from Fraktal SAS Programming)|Enrich your basic data design by adding fields with a SAS technique for fast left outer joins.]] | + | * [[SAS Formats (from Fraktal SAS Programming)|'''Enrich your basic data design''' by adding fields with a SAS technique for fast left outer joins.]] |
'''So, the answer is: ''"Data structures are the key to flexibility and efficiency in SAS programming!"''''' | '''So, the answer is: ''"Data structures are the key to flexibility and efficiency in SAS programming!"''''' | ||
+ | |||
+ | {{SeitenNavigation1 | ||
+ | |links=xx_left.png | ||
+ | |zurück=Programming (from Fraktal SAS Programming) | ||
+ | |rechts=xx_right.png | ||
+ | |vorwärts=Preface (from Fraktal SAS Programming) | ||
+ | |hoch=Duck_zazy_com.png | ||
+ | |übersicht=Fraktal SAS Programming | ||
+ | }} |
Aktuelle Version vom 1. Juli 2014, 13:31 Uhr
Why "Data Structures"?
As in other software systems, SAS makes use of purpose-related data structures, being aware of the advantages emerging from appropriately structured data.
Apart from nowadays well known data tables and data views, SAS provides the programmer with a generalized approach on views beyond SQL views as well as ultra-fast read-only structures for left outer joins and, finally, a metadata repository in physical memory (!) with support for hierarchical modular programming.
- Balancing storage demand, processing speed and flexibility at runtime by properly utilizing Tables and Views in SAS and DBMS.
- Structure and organize your runtime control information to get a maximum of code from a minimum of programming effort.
- Enrich your basic data design by adding fields with a SAS technique for fast left outer joins.
So, the answer is: "Data structures are the key to flexibility and efficiency in SAS programming!"