DOCSLIB.ORG

Powerdesigner 16.6 Data Modeling

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82 Tables (PDM)...............................................................84 Columns (PDM).............................................................101 Primary, Alternate, and Foreign Keys (PDM).........................................117 Indexes (PDM)............................................................. 121 Views (PDM)...............................................................125 Triggers (PDM).............................................................132 Stored Procedures and Functions (PDM).......................................... 150 Users, Groups, and Roles (PDM).................................................166 Synonyms (PDM)...........................................................176 Defaults (PDM).............................................................178 Domains (CDM/LDM/PDM)....................................................181 Sequences (PDM)...........................................................188 Abstract Data Types (PDM)....................................................190 References (PDM)...........................................................193 View References (PDM)...................................................... 202 Business Rules (CDM/LDM/PDM)...............................................205 Lifecycles (PDM)...........................................................209 Data Modeling 2 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Content Tablespaces and Storages (PDM)................................................219 Web Services (PDM).........................................................221 1.4 Multidimensional Diagrams...................................................... 234 Identifying Fact and Dimension Tables............................................236 Generating Cubes...........................................................237 Facts (PDM)...............................................................238 Dimensions (PDM).......................................................... 241 Associations (PDM)......................................................... 246 Operational to Warehouse Data Mappings..........................................247 Generating Data Warehouse Extraction Scripts......................................248 Generating Cube Data........................................................250 1.5 Checking a Data Model..........................................................251 Abstract Data Type Checks (PDM)...............................................252 Abstract Data Type Procedure Checks (PDM).......................................253 Association Checks (CDM).................................................... 254 Association Checks (PDM).................................................... 255 Column Checks (PDM).......................................................256 Cube Checks (PDM).........................................................258 Database Checks (PDM)......................................................259 Database Package Checks (PDM)...............................................260 Database Package Sub-Object Checks (PDM).......................................261 Data Format Checks (CDM/LDM/PDM)...........................................262 Data Item Checks (CDM)......................................................262 Data Source Checks (PDM)....................................................263 Default Checks (PDM)........................................................264 Dimension Checks (PDM).....................................................265 Domain Checks (CDM/LDM/PDM).............................................. 266 Entity Attribute Checks (CDM/LDM)............................................. 268 Entity Identifier Checks (CDM/LDM)............................................. 269 Entity Checks (CDM/LDM)....................................................270 Fact Checks (PDM)..........................................................271 Fact Measure, Dimension Hierarchy, and Attribute Checks (PDM).........................272 Horizontal and Vertical Partitioning and Table Collapsing Checks (PDM)....................273 Index and View Index Checks (PDM)..............................................274 Inheritance Checks (CDM/LDM)................................................ 275 Join Index Checks (PDM)......................................................276 Key Checks (PDM)..........................................................277 Lifecycle and Lifecycle Phase Checks (PDM)........................................278 Package Checks (CDM/LDM/PDM)..............................................279 Procedure Checks (PDM)..................................................... 281 Reference and View Reference Checks (PDM).......................................282 Data Modeling Content © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3 Relationship Checks (CDM/LDM)............................................... 283 Sequence Checks (PDM)......................................................284 Synonym Checks (PDM)......................................................285 Table and View Checks (PDM)..................................................285 Tablespace and Storage Checks (PDM)...........................................288 Trigger and DBMS Trigger Checks (PDM)..........................................289 User, Group, and Role Checks (PDM).............................................289 View Checks (PDM).........................................................290 Web Service and Web Operation Checks (PDM)......................................291 1.6 Generating and Reverse-Engineering Databases........................................292 Writing SQL Code in PowerDesigner..............................................292 Previewing SQL Statements................................................... 296 Connecting to a Database.....................................................300 Generating a Database from a PDM..............................................302 Generating an SAP BusinessObjects Universe.......................................313 Generating Test Data to a Database..............................................317 Estimating Database Size.....................................................320 Modifying a Database........................................................322 Displaying Data from a Database................................................325 Reverse Engineering a Database into a PDM........................................326 Reverse-Engineering an SAP BusinessObjects Universe................................337 Archive PDMs..............................................................339 1.7 Generating Other Models from a Data Model..........................................339 Generating Other Models from a CDM............................................ 340 Generating Other Models from an LDM............................................344 Generating Other Models from a PDM............................................ 344 1.8 Migrating from ERwin to PowerDesigner.............................................350 Importing Individual ERwin Files.................................................351 Importing Multiple ERwin Files..................................................352 Post-Import...............................................................354 PowerDesigner vs ERwin Terminology............................................354 Getting Started Using PowerDesigner for Former ERwin Users...........................356 2 DBMS Definition Reference.....................................................359 2.1 Hadoop Hive.................................................................359 Partitions and Partition Values (Hadoop Hive).......................................361 2.2 HP Neoview................................................................. 362 Materialized View Groups (Neoview)............................................. 366 2.3 IBM
Recommended publications
  • Customizing and Extending Powerdesigner SAP Powerdesigner Documentation Collection Content

    Customizing and Extending Powerdesigner SAP Powerdesigner Documentation Collection Content

    User Guide PUBLIC SAP PowerDesigner Document Version: 16.6.2 – 2017-01-05 Customizing and Extending PowerDesigner SAP PowerDesigner Documentation Collection Content 1 PowerDesigner Resource Files.................................................... 9 1.1 Opening Resource Files in the Editor.................................................10 1.2 Navigating and Searching in Resource Files............................................ 11 1.3 Editing Resource Files........................................................... 13 1.4 Saving Changes................................................................13 1.5 Sharing and Embedding Resource Files...............................................13 1.6 Creating and Copying Resource Files.................................................14 1.7 Specifying Directories to Search for Resource Files.......................................15 1.8 Comparing Resource Files........................................................ 15 1.9 Merging Resource Files.......................................................... 16 2 Extension Files................................................................18 2.1 Creating an Extension File.........................................................19 2.2 Attaching Extensions to a Model....................................................20 2.3 Exporting an Embedded Extension File for Sharing.......................................21 2.4 Extension File Properties......................................................... 21 2.5 Example: Adding a New Attribute from a Property
  • Modeling Data Heritage with Sybase Powerdesigner®

    Modeling Data Heritage with Sybase Powerdesigner®

    MODELING DATA HERITAGE WITH SYBASE POWERDESIGNER® THE ENTERPRISE. UNWIRED. WHITE PAPER Knowing where our data came from and where it is going is one of the most challenging aspects of managing today’s data center. As our systems become more integrated and interdependent, through replication, ware- housing and system integration efforts, the impact of a change on any data element can be huge. Having the ability to document, and then report on, data heritage, allows users to more effectively and efficiently predict the impact of a change, as well as streamline its implementation. Managing Data Heritage, the sources and targets of data, require a 21st century modeling tool like Sybase PowerDesigner. REQUIREMENTS FOR MANAGING DATA HERITAGE When managing data heritage, it is important to be able to clearly document the data elements (aliases, format, statistics and other quality indicators), document the sourcing information and target data systems information (including transformation rules), and stewardship information (who created and modified the data elements, security and access rights and history). Starting with the processes, users need to be able to trace to all data elements (and any interim elements) to all final implementation points. To achieve this, users need to document: ■ All data processes with business definitions and requirements ■ All data items at a conceptual level with business definitions and stewardship details ■ All physical data (Tables/Columns) with version history ■ All dependencies between source and target tables and columns A TOOLSET AND A SOLUTION: BUILDING BLOCKS FOR DATA HERITAGE To address these needs, PowerDesigner offers rich process modeling, data analysis and design techniques that capture and manage the dependency metadata needed to document data heritage.
  • Denormalization Strategies for Data Retrieval from Data Warehouses

    Denormalization Strategies for Data Retrieval from Data Warehouses

    Decision Support Systems 42 (2006) 267–282 www.elsevier.com/locate/dsw Denormalization strategies for data retrieval from data warehouses Seung Kyoon Shina,*, G. Lawrence Sandersb,1 aCollege of Business Administration, University of Rhode Island, 7 Lippitt Road, Kingston, RI 02881-0802, United States bDepartment of Management Science and Systems, School of Management, State University of New York at Buffalo, Buffalo, NY 14260-4000, United States Available online 20 January 2005 Abstract In this study, the effects of denormalization on relational database system performance are discussed in the context of using denormalization strategies as a database design methodology for data warehouses. Four prevalent denormalization strategies have been identified and examined under various scenarios to illustrate the conditions where they are most effective. The relational algebra, query trees, and join cost function are used to examine the effect on the performance of relational systems. The guidelines and analysis provided are sufficiently general and they can be applicable to a variety of databases, in particular to data warehouse implementations, for decision support systems. D 2004 Elsevier B.V. All rights reserved. Keywords: Database design; Denormalization; Decision support systems; Data warehouse; Data mining 1. Introduction houses as issues related to database design for high performance are receiving more attention. Database With the increased availability of data collected design is still an art that relies heavily on human from the Internet and other sources and the implemen- intuition and experience. Consequently, its practice is tation of enterprise-wise data warehouses, the amount becoming more difficult as the applications that data- of data that companies possess is growing at a bases support become more sophisticated [32].Cur- phenomenal rate.
  • OLAP, Relational, and Multidimensional Database Systems

    OLAP, Relational, and Multidimensional Database Systems

    OLAP, Relational, and Multidimensional Database Systems George Colliat Arbor Software Corporation 1325 Chcseapeakc Terrace, Sunnyvale, CA 94089 Introduction Many people ask about the difference between implementing On-Line Analytical Processing (OLAP) with a Relational Database Management System (ROLAP) versus a Mutidimensional Database (MDD). In this paper, we will show that an MDD provides significant advantages over a ROLAP such as several orders of magnitude faster data retrieval, several orders of magnitude faster calculation, much less disk space, and le,~ programming effort. Characteristics of On-Line Analytical Processing OLAP software enables analysts, managers, and executives to gain insight into an enterprise performance through fast interactive access to a wide variety of views of data organized to reflect the multidimensional aspect of the enterprise data. An OLAP service must meet the following fundamental requirements: • The base level of data is summary data (e.g., total sales of a product in a region in a given period) • Historical, current, and projected data • Aggregation of data and the ability to navigate interactively to various level of aggregation (drill down) • Derived data which is computed from input data (performance rados, variance Actual/Budget,...) • Multidimensional views of the data (sales per product, per region, per channel, per period,..) • Ad hoc fast interactive analysis (response in seconds) • Medium to large data sets ( 1 to 500 Gigabytes) • Frequently changing business model (Weekly) As an iUustration we will use the six dimension business model of a hypothetical beverage company. Each dimension is composed of a hierarchy of members: for instance the time dimension has months (January, February,..) as the leaf members of the hierarchy, Quarters (Quarter 1, Quarter 2,..) as the next level members, and Year as the top member of the hierarchy.
  • A Comprehensive Analysis of Sybase Powerdesigner 16.0

    A Comprehensive Analysis of Sybase Powerdesigner 16.0

    white paper A Comprehensive Analysis of Sybase® PowerDesigner® 16.0 InformationArchitect vs. ER/Studio XE2 Version 2.0 www.sybase.com TABLe OF CONTENtS 1 Introduction 1 Product Overviews 1 ER/Studio XE2 3 Sybase PowerDesigner 16.0 4 Data Modeling Activities 4 Overview 6 Types of Data Model 7 Design Layers 8 Managing the SAM-LDM Relationship 10 Forward and Reverse Engineering 11 Round-trip Engineering 11 Integrating Data Models with Requirements and Processes 11 Generating Object-oriented Models 11 Dependency Analysis 17 Model Comparisons and Merges 18 Update Flows 18 Required Features for a Data Modeling Tool 18 Core Modeling 25 Collaboration 27 Interfaces & Integration 29 Usability 34 Managing Models as a Project 36 Dependency Matrices 37 Conclusions 37 Acknowledgements 37 Bibliography 37 About the Author IntrOduCtion Data modeling is more than just database design, because data doesn’t just exist in databases. Data does not exist in isolation, it is created, managed and consumed by business processes, and those business processes are implemented using a variety of applications and technologies. To truly understand and manage our data, and the impact of changes to that data, we need to manage more than just models of data in databases. We need support for different types of data models, and for managing the relationships between data and the rest of the organization. When you need to manage a data center across the enterprise, integrating with a wider set of business and technology activities is critical to success. For this reason, this review will use the InformationArchitect version of Sybase PowerDesigner rather than their DataArchitect™ version.
  • Data Modeler User's Guide

    Data Modeler User's Guide

    Oracle® SQL Developer Data Modeler User's Guide Release 18.1 E94838-01 March 2018 Oracle SQL Developer Data Modeler User's Guide, Release 18.1 E94838-01 Copyright © 2008, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
  • New Features Summary SAP Powerdesigner Documentation Collection Company

    New Features Summary SAP Powerdesigner Documentation Collection Company

    USER GUIDE | PUBLIC SAP PowerDesigner Document Version: 16.7.00 – 2020-04-03 New Features Summary SAP PowerDesigner Documentation Collection company. All rights reserved. All rights company. affiliate THE BEST RUN 2020 SAP SE or an SAP SE or an SAP SAP 2020 © Content 1 New Features v16.7...........................................................3 2 New Features v16.6 SP10...................................................... 5 3 New Features v16.6 SP09......................................................7 4 New Features v16.6 SP08......................................................9 5 New Features v16.6 SP07......................................................11 6 New Features v16.6 SP06.....................................................15 7 New Features v16.6 SP05..................................................... 18 7.1 New PowerDesigner Web Features v16.6 SP05........................................18 7.2 New Requirements Model Features v16.6 SP05.......................................19 7.3 New Enterprise Architecture Model Features v16.6 SP05.................................19 7.4 New Business Process Model Features v16.6 SP05.....................................21 7.5 New Data Model Features v16.6 SP05..............................................21 8 New Features v16.6 SP04.....................................................23 8.1 New Web Client Features.......................................................23 8.2 New Desktop Client Features....................................................29 9 New Features v16.6 SP03....................................................
  • On Active Deductive Databases

    On Active Deductive Databases

    On Active Deductive Databases The Statelog Approach Georg Lausen Bertram Ludascher Wolfgang May Institut fur Informatik Universitat Freiburg Germany flausenludaeschmayginfo rmat ikun ifr eibur gde Abstract After briey reviewing the basic notions and terminology of active rules and relating them to pro duction rules and deductive rules resp ectively we survey a number of formal approaches to active rules Subsequentlywe present our own stateoriented logical approach to ac tive rules which combines the declarative semantics of deductive rules with the p ossibility to dene up dates in the style of pro duction rules and active rules The resulting language Statelog is surprisingly simple yet captures many features of active rules including comp osite eventde tection and dierent coupling mo des Thus it can b e used for the formal analysis of rule prop erties like termination and expressivepo wer Finally weshowhow nested transactions can b e mo deled in Statelog b oth from the op erational and the mo deltheoretic p ersp ective Intro duction Motivated by the need for increased expressiveness and the advent of new appli cations rules have b ecome very p opular as a paradigm in database programming since the late eighties Min Today there is a plethora of quite dierent appli cation areas and semantics for rules From a birdseye view deductive and active rules may b e regarded as two ends of a sp ectrum of database rule languages Deductive Rules Production Rules Active Rules higher level lower level stratied well RDL pro ARDL Ariel Starburst Postgres
  • Multidimensional Network Analysis

    Multidimensional Network Analysis

    Universita` degli Studi di Pisa Dipartimento di Informatica Dottorato di Ricerca in Informatica Ph.D. Thesis Multidimensional Network Analysis Michele Coscia Supervisor Supervisor Fosca Giannotti Dino Pedreschi May 9, 2012 Abstract This thesis is focused on the study of multidimensional networks. A multidimensional network is a network in which among the nodes there may be multiple different qualitative and quantitative relations. Traditionally, complex network analysis has focused on networks with only one kind of relation. Even with this constraint, monodimensional networks posed many analytic challenges, being representations of ubiquitous complex systems in nature. However, it is a matter of common experience that the constraint of considering only one single relation at a time limits the set of real world phenomena that can be represented with complex networks. When multiple different relations act at the same time, traditional complex network analysis cannot provide suitable an- alytic tools. To provide the suitable tools for this scenario is exactly the aim of this thesis: the creation and study of a Multidimensional Network Analysis, to extend the toolbox of complex network analysis and grasp the complexity of real world phenomena. The urgency and need for a multidimensional network analysis is here presented, along with an empirical proof of the ubiquity of this multifaceted reality in different complex networks, and some related works that in the last two years were proposed in this novel setting, yet to be systematically defined. Then, we tackle the foundations of the multidimensional setting at different levels, both by looking at the basic exten- sions of the known model and by developing novel algorithms and frameworks for well-understood and useful problems, such as community discovery (our main case study), temporal analysis, link prediction and more.
  • Integration Definition for Function Modeling (IDEF0)

    Integration Definition for Function Modeling (IDEF0)

    NIST U.S. DEPARTMENT OF COMMERCE PUBLICATIONS £ Technology Administration National Institute of Standards and Technology FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) » Category: Software Standard SUBCATEGORY: MODELING TECHNIQUES 1993 December 21 183 PUB FIPS JK- 45C .AS A3 //I S3 IS 93 FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) Category: Software Standard Subcategory: Modeling Techniques Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Issued December 21, 1993 U.S. Department of Commerce Ronald H. Brown, Secretary Technology Administration Mary L. Good, Under Secretary for Technology National Institute of Standards and Technology Arati Prabhakar, Director Foreword The Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official publication relating to standards and guidelines adopted and promulgated under the provisions of Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235. These mandates have given the Secretary of Commerce and NIST important responsibilities for improving the utilization and management of computer and related telecommunications systems in the Federal Government. The NIST, through its Computer Systems Laboratory, provides leadership, technical guidance,
  • Metamodeling and Method Engineering with Conceptbase”

    Metamodeling and Method Engineering with Conceptbase”

    This is a pre-print of the book chapter M. Jeusfeld: “Metamodeling and method engineering with ConceptBase” . In Jeusfeld, M.A., Jarke, M., Mylopoulos, J. (eds): Metamodeling for Method Engineering, pp. 89-168. The MIT Press., 2009; the original book is available from MIT Press http://mitpress.mit.edu/node/192290 This pre-print may only be used for scholar, non-commercial purposes. Most of the sources for the examples in this chapter are available via http://merkur.informatik.rwth-aachen.de/pub/bscw.cgi/3782591 for download. They require ConceptBase 7.0 or later available from http://conceptbase.cc. Metamodeling and Method Engineering with ConceptBase Manfred Jeusfeld Abstract. This chapter provides a practical guide on how to use the meta data repository ConceptBase to design information modeling methods by using meta- modeling. After motivating the abstraction principles behind meta-modeling, the language Telos as realized in ConceptBase is presented. First, a standard factual representation of statements at any IRDS abstraction level is defined. Then, the foundation of Telos as a logical theory is elaborated yielding simple fixpoint semantics. The principles for object naming, instantiation, attribution, and specialization are reflected by roughly 30 logical axioms. After the language axiomatization, user-defined rules, constraints and queries are introduced. The first part is concluded by a description of active rules that allows the specification of reactions of ConceptBase to external events. The second part applies the language features of the first part to a full-fledged information modeling method: The Yourdan method for Modern Structured Analysis. The notations of the Yourdan method are designed along the IRDS framework.
  • Customizing and Extending Powerdesigner SAP Powerdesigner Documentation Collection Company

    Customizing and Extending Powerdesigner SAP Powerdesigner Documentation Collection Company

    USER GUIDE | PUBLIC SAP PowerDesigner Document Version: 16.7.00 – 2020-04-03 Customizing and Extending PowerDesigner SAP PowerDesigner Documentation Collection company. All rights reserved. All rights company. affiliate THE BEST RUN 2020 SAP SE or an SAP SE or an SAP SAP 2020 © Content 1 PowerDesigner Resource Files..................................................9 1.1 Opening Resource Files in the Editor...............................................10 1.2 Navigating and Searching in Resource Files..........................................12 1.3 Editing Resource Files.........................................................13 1.4 Saving Changes............................................................. 13 1.5 Sharing and Embedding Resource Files.............................................13 1.6 Creating and Copying Resource Files...............................................14 1.7 Specifying Directories to Search for Resource Files.....................................15 1.8 Comparing Resource Files......................................................15 1.9 Merging Resource Files........................................................16 2 Extension Files.............................................................18 2.1 Creating an Extension File......................................................19 2.2 Attaching Extensions to a Model................................................. 20 2.3 Exporting an Embedded Extension File for Sharing.....................................21 2.4 Extension File Properties.......................................................21