DOCSLIB.ORG

Java Database Technologies (Part I)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Java Database Technologies (Part I) Extreme Java G22.3033-007 Session 12 - Main Theme Java Database Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Summary of Previous Session Applications of Java to Database Technology Database Technology Review Basic and Advanced JDBC Features J2EE Enterprise Data Enabling XML and Database Technology Readings Class Project & Assignment #5a 2 1 Summary of Previous Session Summary of Previous Session Enterprise JavaBeans (EJBs) J2EE Connector Architecture Practical Survey of Mainstream J2EE App. Servers Web Services Developer Pack Enterprise Application Integration (EAI) and Business to Business Integration (B2Bi) J2EE Blueprint Programs Class Project & Assignment #4c 3 Part I Java and Database Technology Also See Session 12 Handout on: “Java and Database Technology (JDBC)” and Session 12 Presentation on: “Designing Databases for eBusiness Solutions” 4 2 Review of Database Technology Introduction to Database Technology Data Modeling Conceptual Database Design Logical Database Design Physical Database Design Database System Programming Models Database Architectures Database Storage Management Database System Administration Commercial Systems: www.oracle.com,www.ibm.com/db2, http://www- 3.ibm.com/software/data/informix/,www.sybase.com 5 Advanced Database Concepts Parallel and Distributed Databases Web Databases Data Warehousing and Data Mining Mobile Databases Spatial and Multimedia Databases Geographic Information Systems Active Databases Temporal Databases Deductive Databases 6 3 Java and Database Technology JavaSpaces Create and store objects with persistence Allow process integrity http://www.javasoft.com/products/javaspaces/index.html JDBC Data Access API Access tabular data sources from Java http://www.javasoft.com/products/jdbc/index.html J2EE database access and container managed persistence (http://java.sun.com/j2ee/j2sdkee/techdocs/guides/ejb/html/DevGuideTOC.html) Pjama: Orthogonal Persistence for the Java Platform http://www.sun.com/research/forest/opj.main.html http://www.dcs.gla.ac.uk/pjava/ 7 JDBC: Pure Java and ODBC-Drivers 8 4 Basic and Advanced JDBC See Session 12 Handouts: Java and Database Technology - JDBC Enterprise JavaBeans Patterns See Session 12 Demo Programs on JDBC Java databases http://sourceforge.net/projects/hsql/ http://www.pointbase.com/ 9 JDBC API 3.0 (http://java.sun.com/products/jdbc/index.html, http://www.wiley.com/extras/jdbc_3_java_db_connectivity/) JDBC Technology Core features (java.sql package) Scrollable result sets Updatable result sets Batch updates Savepoints JDBC Optional Package features (javax.sql package) JNDI support Connection pooling Distributed transactions Rowset objects (JavaBeans) Statement pooling 10 5 URL-Based Database Connection 11 Java and ODBs Related Developments: Persistent Object Stores Object-Oriented Database Management Systems Object/Relational Mapping Automation See Object-Oriented Database Articles at http://www.odbmsfacts.com/ Java Data Objects (JDO) API (http://access1.sun.com/jdo) Transparent database access Suitable implementation for Persistent helper classes for session beans Delegate classes for BMP Entity Beans Delegate classes for CMP Entity Beans 12 6 Part II Introduction to J2EE Enterprise Data Enabling Also See Session 12 Handouts on: “Enterprise JavaBeans Patterns” “Persistence in EJB Frameworks” “Efficient CMP Development” 13 Entity Beans in EJB Application Servers Represent sets of data (all or part of a database table or a view) Functionality limited to creation, update, and deletion of data Manage persistence of data Maintained in a cache Can be container or bean managed Container-managed beans are under the control of an application server for persistence and transaction management Container-managed beans are restricted in the type and complexity of data they can manage Bean-managed beans rely on user provided code for persistence and transaction management 14 7 Session Beans in EJB Application Servers Handle the business logic of EJB applications May use multiple entity beans to gather application data 15 EJB Component/Programming Model 16 8 Anatomy of a CMP Bean EJB remote interface (extends javax.ejb.EJBObject) Contains method signatures for any method that accesses or modifies data stored in the bean EJB remote implementation (implements javax.ejb.EntityBean) Provides an implementation of all the methods defined in the remote interface, in addition to methods required by the application server EJB home interface (extends javax.ejb.EJBHome interface) Declares method signatures for any method that creates new instances of the bean, and for all methods that are used to retrieve instances of the bean (finder methods EJB key Contains the unique primary key implementation for the bean any class that is a legal value type in RMI-IIOP 17 Anatomy of a CMP Bean (continued) EJB finder helper interface (optional) Contains one static java.lang.String field for each finder method declared in the EJB home interface Strings are initialized with SQL queries executed dynamically when bean instances are retrieved in a finder method Some server ignore this file and put queries in XML deployment descriptors using proprietary query language formats Deployment descriptor (XML -> serialized data object) Names of EJB classes/interfaces, list of persistent fields, etc. Database scripts Application server may generate them 18 9 EJB Implementation Process (WSAD) Create EJB Project Create (Stateful) Session Beans Create CMP Entity Beans Create CMRs as needed (EJB 2.0 Assumed) Create custom finder methods using EJB QL as needed Map CMP Entity Beans to a Relational Database Specify J2EE References to EJBs and Resources Required by EJBs Integrate EJBs with Web Module “Model” Objects as Needed 19 EJB Generation (e.g., IBM EJBMaker, BEA WebGain Studio) <?xml version="1.0"?> <!DOCTYPE ejbmaker SYSTEM "ejbmaker.dtd"> <ejbmaker> <!—default attributes for beans --> <transaction-attr>TX_REQUIRED</transaction-attr> <isolation-level>SERIALIZABLE</isolation-level> <run-as-mode>SPECIFIED_IDENTITY</run-as-mode> <re-entrant>false</re-entrant> <!—A Simple Account CMP entity EJB --> <bean name = "Account" type = "entity"> <persistent_field dt="int" col_dt="INTEGER"> ACCTNUMBER </persistent_field> <persistent_field dt="java.lang.String" col_dt="VARCHAR(13)"> SSN </persistent_field> <persistent_field dt="double" col_dt="DOUBLE"> BALANCE </persistent_field> <finder_method name="findNegativeAcct"> <sql> SELECT * FROM EJB.ACCOUNTBEANTBL WHERE BALANCE &lt; 0 </sql> </finder_method> </bean> 20 </ejbmaker> 10 EJB 2.0 Query Language: EJB QL SQL-like language for expressing selection criteria over the domain of 2.0 CMP EJBs Database-agnostic query language that can be mapped to virtually any relational backend Used to implement EJB custom finders Look under the “Bean” tab of the EJB deployment descriptor in WSAD and scroll down to “Queries | Add” e.g., SELECT OBJECT(i) FROM Inventory i WHERE i.category=?1 Also used to implement ejbSelect() methods, which are EJB queries accessible to the bean implementation only 21 SQLJ (www.sqlj.org) Defines the “style” of database access JDBC implies “dynamic” access SQLJ is a standard for static SQL usage Provides performance enhancements over dynamic SQL Provides “SELECT INTO” statement to populate Java variables directly from the result of an SQLJ statement (no need for cursors) Three stages required SQLJ code generation Translation of SQLJ code to Java Profiling of Java code against specific database used 22 11 IBM WAS Persistence Extensions Access Intent Default is “Pessimistic Update with weakest lock at load”) Application Profile (provides “dynamic” access intent) EJB Persistence Support Extensions (e.g., EJB inheritance) EJB QL Extensions (e.g., ORDER BY) Transactions (unit-of-work scoping) Support for JCA and JDNC-based local transactions to define what goes on when the transaction context is “unspecified” as per the EJB 2.0 specification ActivitySession Service Goal is to retain contained EJBs beyond a given transaction 23 Container Managed Persistence Architecture (review) 24 12 Bean Managed Persistence Architecture (review) 25 JDBC in the J2EE Architecture 26 13 EJB Persistence Service Architecture See Persistence Service Interface for Entity Beans: http://jsp.java.sun.com/javaone/javaone2000/pdfs/TS-1498.pdf See Jboss Persistence Manager Architecture: JAWS (Just Another Web Store) is the default CMP (Container Manager Persistence) plugin that performs basic O/R functionality against a JDBC-store See Patterns for Object Relational Access Layers http://www.objectarchitects.de/ObjectArchitects/orpatterns/EJBPersistence See Session 13 Handout on “Persistence in EJB Frameworks” 27 EJB Development Approach #1 Handcode Everything: EJB remote interface EJB remote implementation EJB home interface EJB key EJB finder helper interface Deployment descriptor Database scripts 28 14 EJB Development Approach #2: Handcode the Bean and Descriptor 29 EJB Development Approach #3: Graphical Bean and Descriptor Generator 30 15 Persistence Service Performance Issues Complexity of an optimal access layer Object to Tuple Layer Logical Mapping Physical Layer Mapping Caching to reduce database traffic and disk I/O Data Clustering Application must still be maintainable at a reasonable cost See Session 12 Handouts
Load more

Recommended publications
  • Lesson 17 Building Xqueries in Xquery Editor View
    AquaLogic Data Services Platform™ Tutorial: Part II A Guide to Developing BEA AquaLogic Data Services Platform (DSP) Projects Note: This tutorial is based in large part on a guide originally developed for enterprises evaluating Data Services Platform for specific requirements. In some cases illustrations, directories, and paths reference Liquid Data, the previous name of the Data Services Platform. Version: 2.1 Document Date: June 2005 Revised: June 2006 Copyright Copyright © 2005, 2006 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent, in writing, from BEA Systems, Inc. Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software- Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent. Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems.
    [Show full text]
  • Rdbmss Why Use an RDBMS
    RDBMSs • Relational Database Management Systems • A way of saving and accessing data on persistent (disk) storage. 51 - RDBMS CSC309 1 Why Use an RDBMS • Data Safety – data is immune to program crashes • Concurrent Access – atomic updates via transactions • Fault Tolerance – replicated dbs for instant failover on machine/disk crashes • Data Integrity – aids to keep data meaningful •Scalability – can handle small/large quantities of data in a uniform manner •Reporting – easy to write SQL programs to generate arbitrary reports 51 - RDBMS CSC309 2 1 Relational Model • First published by E.F. Codd in 1970 • A relational database consists of a collection of tables • A table consists of rows and columns • each row represents a record • each column represents an attribute of the records contained in the table 51 - RDBMS CSC309 3 RDBMS Technology • Client/Server Databases – Oracle, Sybase, MySQL, SQLServer • Personal Databases – Access • Embedded Databases –Pointbase 51 - RDBMS CSC309 4 2 Client/Server Databases client client client processes tcp/ip connections Server disk i/o server process 51 - RDBMS CSC309 5 Inside the Client Process client API application code tcp/ip db library connection to server 51 - RDBMS CSC309 6 3 Pointbase client API application code Pointbase lib. local file system 51 - RDBMS CSC309 7 Microsoft Access Access app Microsoft JET SQL DLL local file system 51 - RDBMS CSC309 8 4 APIs to RDBMSs • All are very similar • A collection of routines designed to – produce and send to the db engine an SQL statement • an original
    [Show full text]
  • Eclipselink Understanding Eclipselink 2.4
    EclipseLink Understanding EclipseLink 2.4 June 2013 EclipseLink Concepts Guide Copyright © 2012, 2013, by The Eclipse Foundation under the Eclipse Public License (EPL) http://www.eclipse.org/org/documents/epl-v10.php The initial contribution of this content was based on work copyrighted by Oracle and was submitted with permission. Print date: July 9, 2013 Contents Preface ............................................................................................................................................................... xiii Audience..................................................................................................................................................... xiii Related Documents ................................................................................................................................... xiii Conventions ............................................................................................................................................... xiii 1 Overview of EclipseLink 1.1 Understanding EclipseLink....................................................................................................... 1-1 1.1.1 What Is the Object-Persistence Impedance Mismatch?.................................................. 1-3 1.1.2 The EclipseLink Solution.................................................................................................... 1-3 1.2 Key Features ...............................................................................................................................
    [Show full text]
  • Lecture 10: Database Connectivity
    Outline Persistence via Database Lecture 10: JDBC (Java Database Connectivity) Database Connectivity JDBC API -JDBC Wendy Liu CSC309F – Fall 2007 1 2 Java Persistence JDBC (Java Database Relational Database Connectivity) Management System Object relational (RDBMS) Persistence via Database mapping Object-oriented Java Data Object Database Management (JDO) System (OODBMS) Enterprise JavaBean (EJB) 3 4 Three Tier Architecture Database Advantages Data Safety data is immune to program crashes Concurrent Access atomic updates via transactions Fault Tolerance replicated DBs for instant fail-over on machine/disk crashes Data Integrity aids to keep data meaningful Scalability Database can handle small/large quantities of data in a uniform manner A way of saving and accessing structured data on Reporting persistent (disk) storage easy to write SQL programs to generate arbitrary reports 5 6 1 Relational Database Movie Database Example First published by Edgar F. Codd in 1970 A relational database consists of a collection showtimes of tables showtimeid movieid theaterid sdate stime available 1 1 1 3/20/2005 20:00:00 90 A table consists of rows and columns 2 1 1 3/20/2005 22:00:00 90 orders Each row represents a record orderid userid showtimeid 11 1 Each column represents an attribute of the records contained in the table 7 8 RDBMS Technology Client/Server Databases Derby, Oracle, Sybase, MySQL, PointBase, SQLServer JDBC Embedded Databases (Java DataBase Connectivity) Derby,PointBase Personal Databases Access 9 10
    [Show full text]
  • Embedded Database for Remote Process Management System
    Embedded Database for Remote Process Management System {tag} {/tag} IJCA Proceedings on International Conference on Emerging Frontiers in Technology for Rural Area (EFITRA-2012) © 2012 by IJCA Journal EFITRA - Number 4 Year of Publication: 2012 Authors: Kalyani N. Satone Madhuri M . Pal {bibtex}efitra1030.bib{/bibtex} Abstract This paper investigates embedded databases for the MicroBaseJ project. The paper aims at the development of an integrated database and a user interface for a typical 3G mobile phone with Java MIDP2 capability. One of the key objectives is to target a generic solution. A number of commercial sectors could benefit from this solution such as horticulture, building management, pollution/water management, industry etc. Four embedded databases based on J2ME have been investigated. Two of the four have been evaluated and analyzed. The size of processed data is limited to 20000 records when using the wireless toolkit simulator and 11000 records when using a mobile phone. 1 / 3 Embedded Database for Remote Process Management System Refer ences - Mobile and World, &quot;Subscriber statistics end Q1 2007,&quot; 2007. - S. Ravi, M. Chathish, and H. Prasanna, &quot;WAP AND SMS BASED EMERGING TECHNIQUES FOR REMOTEMONITORING AND CONTROL OF A PROCESS PLANT,&quot; in ICSP&apos;04. 2004 7th International Conference, 2004, pp. 2672-2675. - K. Hung and Y. Zhang, &quot;Implementation of a WAP-Based Telemedicine System for Patient Monitoring,&quot; Information Technology in Biomedicine, vol. IEEE Transations on vol. 7, pp. 101-107, June 2003. - M. Nikolova, F. Meijs, and P. Voorwinden, &quot;Remote Mobile Control of Home appliances,&quot; Consumer Electronis, vol.
    [Show full text]
  • Dynamic Information with IBM Infosphere Data Replication CDC
    Front cover IBM® Information Management Software Smarter Business Dynamic Information with IBM InfoSphere Data Replication CDC Log-based for real-time high volume replication and scalability High throughput replication with integrity and consistency Programming-free data integration Chuck Ballard Alec Beaton Mark Ketchie Anzar Noor Frank Ketelaars Judy Parkes Deepak Rangarao Bill Shubin Wim Van Tichelen ibm.com/redbooks International Technical Support Organization Smarter Business: Dynamic Information with IBM InfoSphere Data Replication CDC March 2012 SG24-7941-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (March 2012) This edition applies to Version 6.5 of IBM InfoSphere Change Data Capture (product number 5724-U70). © Copyright International Business Machines Corporation 2012. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi The team who wrote this book . xii Now you can become a published author, too! . xvi Comments welcome. xvii Stay connected to IBM Redbooks . xvii Chapter 1. Introduction and overview . 1 1.1 Optimized data integration . 2 1.2 InfoSphere architecture . 4 Chapter 2. InfoSphere CDC: Empowering information management. 9 2.1 The need for dynamic data . 10 2.2 Data delivery methods. 11 2.3 Providing dynamic data with InfoSphere CDC . 12 2.3.1 InfoSphere CDC architectural overview . 14 2.3.2 Reliability and integrity . 16 Chapter 3. Business use cases for InfoSphere CDC . 19 3.1 InfoSphere CDC techniques for transporting changed data .
    [Show full text]
  • Java Database Connectivity (JDBC) J2EE Application Model
    Java DataBase Connectivity (JDBC) J2EE application model J2EE is a multitiered distributed application model client machines the J2EE server machine the database or legacy machines at the back end JDBC API JDBC is an interface which allows Java code to execute SQL statements inside relational databases Java JDBC driver program connectivity for Oracle data processing utilities driver for MySQL jdbc-odbc ODBC bridge driver The JDBC-ODBC Bridge ODBC (Open Database Connectivity) is a Microsoft standard from the mid 1990’s. It is an API that allows C/C++ programs to execute SQL inside databases ODBC is supported by many products. The JDBC-ODBC Bridge (Contd.) The JDBC-ODBC bridge allows Java code to use the C/C++ interface of ODBC it means that JDBC can access many different database products The layers of translation (Java --> C --> SQL) can slow down execution. The JDBC-ODBC Bridge (Contd.) The JDBC-ODBC bridge comes free with the J2SE: called sun.jdbc.odbc.JdbcOdbcDriver The ODBC driver for Microsoft Access comes with MS Office so it is easy to connect Java and Access JDBC Pseudo Code All JDBC programs do the following: Step 1) load the JDBC driver Step 2) Specify the name and location of the database being used Step 3) Connect to the database with a Connection object Step 4) Execute a SQL query using a Statement object Step 5) Get the results in a ResultSet object Step 6) Finish by closing the ResultSet, Statement and Connection objects JDBC API in J2SE Set up a database server (Oracle , MySQL, pointbase) Get a JDBC driver
    [Show full text]
  • Investigating a Constraint-Based Approach to Data Quality in Information Systems
    Research Collection Master Thesis Investigating a Constraint-Based Approach to Data Quality in Information Systems Author(s): Probst, Oliver Publication Date: 2013 Permanent Link: https://doi.org/10.3929/ethz-a-009980065 Rights / License: In Copyright - Non-Commercial Use Permitted This page was generated automatically upon download from the ETH Zurich Research Collection. For more information please consult the Terms of use. ETH Library Investigating a Constraint-Based Approach to Data Quality in Information Systems Master Thesis Oliver Probst <[email protected]> Prof. Dr. Moira C. Norrie David Weber Global Information Systems Group Institute of Information Systems Department of Computer Science 8th October 2013 Copyright © 2013 Global Information Systems Group. ABSTRACT Constraints are tightly coupled with data validation and data quality. The author investigates in this master thesis to what extent constraints can be used to build a data quality manage- ment framework that can be used by an application developer to control the data quality of an information system. The conceptual background regarding the definition of data qual- ity and its multidimensional concept followed by a constraint type overview is presented in detail. Moreover, the results of a broad research for existing concepts and technical solu- tions regarding constraint definition and data validation with a strong focus on the JavaTM programming language environment are explained. Based on these insights, we introduce a data quality management framework implementation based on the JavaTM Specification Request (JSR) 349 (Bean Validation 1.1) using a single constraint model which avoids in- consistencies and redundancy within the constraint specification and validation process. This data quality management framework contains advanced constraints like an association con- straint which restricts the cardinalities between entities in a dynamic way and the concept of temporal constrains which allows that a constraint must only hold at a certain point in time.
    [Show full text]
  • Understanding Oracle Toplink
    Oracle® Fusion Middleware Understanding Oracle TopLink 12c (12.2.1.4.0) F16472-02 January 2020 Oracle Fusion Middleware Understanding Oracle TopLink, 12c (12.2.1.4.0) F16472-02 Copyright © 2014, 2020, Oracle and/or its affiliates. All rights reserved. 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.
    [Show full text]
  • Talend Open Studio for Data Quality User Guide
    Talend Open Studio for Data Quality User Guide 6.1.2 Talend Open Studio for Data Quality Adapted for v6.1.2. Supersedes previous releases. Publication date: September 13, 2016 Copyleft This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/ Notices Talend is a trademark of Talend, Inc. All brands, product names, company names, trademarks and service marks are the properties of their respective owners. License Agreement The software described in this documentation is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.html. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software developed at ASM, AntlR, Apache ActiveMQ, Apache Ant, Apache Axiom, Apache Axis, Apache Axis 2, Apache Chemistry, Apache Common Http Client, Apache Common Http Core, Apache Commons, Apache Commons Bcel, Apache Commons Lang, Apache Datafu, Apache Derby Database Engine and Embedded JDBC Driver, Apache Geronimo, Apache HCatalog,
    [Show full text]
  • Database Size Requirements for Schema
    Database Size Requirements For Schema Uncoordinated Jodie exscinds some Kaffir after breakneck Hewitt sought tamely. Angel twill stably. Combustion and interpenetrative Bjorn overcapitalized her extra phytologists brown-nose and incite thereto. When the search used to database size requirements for schema structure of more features that can also note that specifies that include billions of. To meet quick business requirements laid waste to handle although in market dynamics new. As soap a schema suggestion model for NoSQL databases is posed to. Note that TeamCity assumes ownership over your database schema. ADMINGETTABINFO table function retrieve table size. Spspaceused gives you the size of collide the indexes combined The results are usually slightly different theme within 1 On SQL 2012 getting this information on for table level but become deliciously simple SQL Management Studio Right arm on Db Reports Standard Reports Disk usage is table. SELECT stnamessname FROM systables st join sysschemas ss. The decision if building space needs to be deallocated depends on still other. Data Types Schema Types and Schema Evolution. How much life has been used by different objects in HANA database. Unpack the debezium connector offsets for database size schema? Command To Export Mysql Database Schema Tenzing. Writing each phase to exacerbate problems, size for database schema structure and cache and manipulating as. When database schema registry and the appropriate data on the orion platform streamlines data. Is the requirement to heaven all depart the tables memory requirements 'up-front' word too. Very Quciky filling DB schema size Dynatrace Answers. Use to guess, everything but it is used space required to the constraints are for schema? Typical bad effects of redundancy are an unnecessary increase customer database size data often prone to inconsistency and decreases in the efficiency of the.
    [Show full text]
  • Tool Support for Architectural Decision Making in Large Software Intensive Projects
    TECHNISCHE UNIVERSITÄT MÜNCHEN Lehrstuhl für Informatik XIX Tool support for architectural decision making in large software intensive projects Manoj Mahabaleshwar Vollständiger Abdruck der von der Fakultät für Informatik der Technischen Universität München zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) genehmigten Dissertation. Vorsitzender: Univ.-Prof. Dr. Alexander Pretschner Prüfer der Dissertation: 1. Univ.-Prof. Dr. Florian Matthes 2. Univ.-Prof. Dr. Bernd Brügge Die Dissertation wurde am 31.10.2019 bei der Technischen Universität München eingereicht und durch die Fakultät für Informatik am 08.03.2020 angenommen. II Zusammenfassung Während des letztens Jahrzehnts hat sich ein Paradigmenwechsel vollzogen, in der Weise, in der Wissenschaftler und Praktiker Softwarearchitekturen betrachten. Eine Softwarearchitektur wird heutzutage nicht nur als Blaupause gesehen, sondern als eine Menge von Designentscheidungen, die zur Blaupause des zugrundeliegenden Softwaresystems führen. Architekten und Entwick- ler treffen regelmäßig Designentscheidungen, die zum Beispiel die Wahl eines Architekturstils, eines Entwurfsmusters und der zugrundeliegenden IT-Infrastruktur betreffen. Die Dokumen- tation solcher Entscheidungen hilft, in großen Projekten, Fragen zu beantworten wie: „Welche Designentscheidungen wurden bereits getroffen?”, „Welche Architekturelemente und Qualität- sattribute werden von einer Entscheidung beeinflusst?”, „Wer sollte in eine neue Entscheidung involviert sein?”, „Welche ähnlichen
    [Show full text]