DOCSLIB.ORG

Of Modern Databases Especially the Relational One

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Of Modern Databases Especially the Relational One Of Modern Databases Especially the Relational One overview in general November 2012 by Sigrún Gunnarsdóttir Database Administrator ÍSOR - Iceland GeoSurvey Table of contents What is a database? - Spreadsheets or ....? ........................................................................................ 3 Types of databases................................................................................................................................ 4 Storing and securing a Database and accessing information using one ....................................... 4 Database tables and how to manage them ....................................................................................... 5 Database design .................................................................................................................................... 5 Database normalization ....................................................................................................................... 6 What is DBMS? ..................................................................................................................................... 7 The choice of DBMS - Oracle, DB2, Informix, PostgresPlus, MySQL, MS-SQL Server ...??? ..... 8 Going over to a relational database ................................................................................................... 9 Role of DBA ......................................................................................................................................... 11 Some tools for input and output of data ......................................................................................... 11 References ............................................................................................................................................ 15 2012_Of_modern_databases_and_the_relational_one.docx Sigrún Gunnarsdóttir Updated: 16.th November 2012 Page 2 of 15 What is a database? - Spreadsheets or ....? With some Google search (like e.g. “what is a database” or “define:database”) one can find all about that, both the older and more simplified definitions: An organized body of related information A database defines a structure for storing information upto the ones recently used definitions which include computer systems: A database is a structured collection of records or data that is stored in a computer system – (in system files of some DBMS – Database Management System – or just in raw unix textfiles) Modern databases are designed to offer an organized mechanism for storing, managing and retrieving information. They do so through the use of tables. If you’re already familiar with spreadsheets like Microsoft Excel, you’re probably accustomed to storing data in tabular form. Just like Excel tables, database tables consist of columns and rows. If a database is so much like a spreadsheet, why can’t I just use a spreadsheet? Databases are actually much more powerful than spreadsheets .... Here are just a few of the actions that you can perform on a database that would be difficult if not impossible to perform on a spreadsheet: • Retrieve all records that match certain criteria • Update records in bulk • Cross-reference records in different tables • Perform complex aggregate calculations The database used to be an extremely technical term used only by large institutions or companies, however with the rise of computer systems and information technology throughout our culture, the database has so to say become a household term. In order for a database to be truly functional, it must: • store large amounts of records well • be accessed easily • new information and changes should also be fairly easy to input Besides these features, all databases that are created should be built with high data integrity and the ability to recover data if hardware fails. 2012_Of_modern_databases_and_the_relational_one.docx Sigrún Gunnarsdóttir Updated: 16.th November 2012 Page 3 of 15 Types of databases There are several common types of databases and each database type has its own data model (how the data is structured). They include: • Flat Model • Hierarchical Model • Relational Model • Network Model More about the Flat Model and Relational Model here later on, in Going over to a relational database. The Hierarchical Model organizes data into a tree-like structure that allows data tables being represented using parent/child relationships so that each parent can have many children, but each child just one parent. The Network Model uses a flexible way representing data tables and is not restricted to being hierarchical or lattice. The relational model is the most popular type of database and an extremely powerful tool, not only to store information, but to access it as well. Relational databases are organized as tables. A table can have many records and each record can have many fields. Tables are sometimes called a relation. It should be noted that every record (group of fields) in a relational database table has its own primary key: one unique field or some few fields combined that makes it easy to identify a record. Relational databases use a program interface called SQL or Structured Query Language. SQL is currently used on practically all relational databases. Storing and securing a Database and accessing information using one While storing data is a great feature of databases, for many database users the most important feature is quick and simple retrieval of information. Queries are requests to pull specific types of information. No matter what kind of information you store on your database, queries can be created using SQL to help answer both simple and important questions. Databases can be very small (less than 1 MB) or extremely large and complicated (terabytes as in many government databases), however all databases are usually stored and located on hard disk or other types of storage devices and are accessed via computer. Large databases may require separate servers and locations, however many small databases can fit easily as files located on your computer's hard drive. Obviously, many databases store confidential and important information that should not be easily accessed by just anyone. Many databases thus require passwords and other security features in order to access the information. While some databases can be accessed via the internet through a network, other databases are closed systems and can only be accessed on site. 2012_Of_modern_databases_and_the_relational_one.docx Sigrún Gunnarsdóttir Updated: 16.th November 2012 Page 4 of 15 Database tables and how to manage them • Tables are the basic unit of storage in a database. Tables are usually defined by a name, a set of columns, and other optional parameters. For each column, a column name, data type and width, precision, or scale must be specified. • Just like Excel tables, database tables consist of columns and rows. Each column contains a different type of attribute and each row corresponds to a single record. • Using SQL statements, data can be added and removed from the table by rows. Each row represents one data record. Data can also be modified through SQL by removing columns or changing some column value for a record. • Some various software tools can be used to interact with the database, for example SQLPLUS, MS Access, dbVisualizer, Navicat and many, many more, in order to view, insert or update data. More about that later on. Database design Before data entering database tables there are some stages of design. A good design of a database structure in the beginning can prevent levels of complexity at later stages. The main design of a database can take place even before a database management system has been chosen. The main building blocks of a database consist of so called entities, attributes and relationships between the entities. An entity may be defined as a thing which is capable of existing independently and which can be uniquely identified. In other words an entity is anything that might deserve its own table in the database concerned. An entity must have a minimal set of uniquely identifying attributes, which is called the entity's primary key. The relationships between entities can be optional or compulsory. When designing a database you should start with identifying it's entities. This is mostly a matter of talking to some people who will use the database and figuring out what data the system will be working with. An internet shop, as an example, sells products which are ordered by customers. In this one sentence three obvious entities of a database for this shop have already been mentioned, product, order and customer. To decide on entities, what is to be an entity in a database or an attribute or relationship isn't always straightforward though. Sometimes in complex data modelling we can come up with many entities that won't translate directly to tables. A lot of information regarding design of databases can be found on the internet. In software engineering, entity-relationship modeling is a method of database modeling, used to produce a data model of a system, often a relational database, and it‘s requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs. 2012_Of_modern_databases_and_the_relational_one.docx Sigrún Gunnarsdóttir Updated: 16.th November 2012 Page 5 of 15 Database normalization In designing relational databases normalization is used, that is a data-structuring model which ensures data consistency and aviods data duplication,
Load more

Recommended publications
  • Oracle® Exadata and IBM® Netezza® Data Warehouse Appliance
    IBM Software Information Management Oracle® Exadata® and IBM® Netezza® Data Warehouse Appliance compared by Phil Francisco, Vice President, Product Management and Product Marketing, IBM and Mike Kearney, Senior Director, Product Marketing, IBM Information Management Oracle Exadata and IBM Netezza Data Warehouse Appliance compared Contents Introduction Introduction 2 IBM Netezza data warehouse appliances focus on technology designed to query and analyze big data. Online Transaction Processing (OLTP) “ Netezza was part of the inspiration for and data warehousing 3 IBM Netezza data warehouse appliances are disrupting the market. Wishing to exploit data at Query performance 5 Exadata. Teradata was part of the lower costs of operation and ownership, many of our Simplicity of operation 10 inspiration for Exadata. We’d like to customers have moved their data warehouses from Value 14 Oracle. Oracle has now brought Exadata to market, thank them for forcing our hand Conclusion 16 a machine which apparently does everything an IBM and forcing us to go into the Netezza data warehouse appliance does, and also hardware business.” processes online transactions. This examination of Exadata and IBM Netezza as data warehouse — Larry Ellison, January 2010 platforms is written from an unashamedly IBM viewpoint, however to ensure credibility we have taken advice from Philip Howard, Research Director of Bloor Research and Curt Monash, warehouses. More important, our customers create President, Monash Research. new business value by deploying analytic applications which they previously considered To innovate requires us to think and do things beyond their reach. differently, solving a problem using new approaches. IBM Netezza data warehouse appliances deliver “Netezza was part of the inspiration for Exadata.
    [Show full text]
  • Mcafee Database Security Installation Guide
    CONFIDENTIAL McAfee Database Security Installation Guide McAfee Integrity Monitor for Databases McAfee Database Activity Monitoring McAfee Vulnerability Manager for Databases McAfee Vulnerability Manager for Databases End User License Agreement NOTICE TO ALL USERS: PLEASE READ THIS CONTRACT CAREFULLY. BY CLICKING THE ACCEPT BUTTON OR INSTALLING THE SOFTWARE, YOU (EITHER AN INDIVIDUAL OR A SINGLE ENTITY) AGREE THAT THIS AGREEMENT IS ENFORCEABLE LIKE ANY WRITTEN CONTRACT SIGNED BY YOU. IF YOU DO NOT AGREE TO ALL THE TERMS OF THIS AGREEMENT, CLICK ON THE BUTTON THAT INDICATES THAT YOU DO NOT ACCEPT THE TERMS OF THIS CONTRACT AND DO NOT INSTALL THE SOFTWARE. 1. Definitions. a. “Software” means (a) all of the contents of the files, disk(s), CD-ROM(s) or other media (including electronic media) with which this Agreement is provided or such contents as are hosted by McAfee or its distributors, resellers, OEM/MSP partners, or other business partners (collectively “Authorized Partner(s)”), including but not limited to (i) McAfee or third party computer information or software; (ii) related explanatory materials in printed, electronic, or online form (“Documentation”); and (b) upgrades, modified or subsequent versions and updates including any virus or vulnerability updates (collectively “Updates”), and Software, if any, licensed to you by McAfee or an Authorized Partner as part of a maintenance contract or service subscription. b. “Use” or “Using” means to access, install, download, copy or otherwise benefit from using the Software. c. “Permitted Number” means one (1) unless otherwise indicated under a valid license (e.g., volume license) granted by McAfee. d. “Computer” means a device that accepts information in digital or similar form and manipulates it for a specific result based upon a sequence of instructions.
    [Show full text]
  • Query Optimizing for On-Line Analytical Processing Adventures in the Land of Heuristics
    Aalto University School of Science Master's Programme in Computer, Communication and Information Sciences Jonas Berg Query Optimizing for On-line Analytical Processing Adventures in the land of heuristics Master's Thesis Espoo, May 22, 2017 Supervisor: Professor Eljas Soisalon-Soininen Advisors: Jarkko Miettinen M.Sc. (Tech.) Marko Nikula M.Sc. (Tech) Aalto University School of Science Master's Programme in Computer, Communication and In- ABSTRACT OF formation Sciences MASTER'S THESIS Author: Jonas Berg Title: Query Optimizing for On-line Analytical Processing { Adventures in the land of heuristics Date: May 22, 2017 Pages: vii + 71 Major: Computer Science Code: SCI3042 Supervisor: Professor Eljas Soisalon-Soininen Advisors: Jarkko Miettinen M.Sc. (Tech.) Marko Nikula M.Sc. (Tech) Newer database technologies, such as in-memory databases, have largely forgone query optimization. In this thesis, we presented a use case for query optimization for an in-memory column-store database management system used for both on- line analytical processing and on-line transaction processing. To date, the system in question has used a na¨ıve query optimizer for deciding on join order. We went through related literature on the history and evolution of database technology, focusing on query optimization. Based on this, we analyzed the current system and presented improvements for its query processing abilities. We implemented a new query optimizer and experimented with it, seeing how it performed on several queries, concluding that it is a successful improvement
    [Show full text]
  • Mcafee Real-Time Database Monitoring, Auditing, and Intrusion
    White Paper McAfee Real-Time Database Monitoring, Auditing, and Intrusion Prevention Table of Contents Introduction 3 Existing Components of Database Security 3 Authentication and access control 3 Native database audit tools 4 The Network Approach to Database Activity Monitoring 4 The local access challenge 4 The encryption challenge 6 McAfee Database Activity Monitoring: Real-Time Database Monitoring 7 and Intrusion Prevention Unique advantages 11 2 McAfee Real-Time Database Monitoring, Auditing, and Intrusion Prevention Databases store an enterprise’s most valuable information assets, but in most organizations today, they are poorly protected. It’s good common sense to secure databases as well as or better than other systems in the enterprise. But it’s not that simple. In this white paper, we take a look at the shortcomings of the database security tools used by enterprises worldwide and the technology and approach required to provide real-time, comprehensive protection for all types of databases. Components of Database Security A wide array of technologies and tools are currently used to provide various aspects of database security. As with other areas of IT security, no single tool can provide an ironclad defense against all threats and abuses. It’s best to implement a combination of tools to achieve adequate security. The two main categories of tools in use across enterprises large and small are authentication/access “I hack, I ruin, I make piles of control and native database audit tools. money.” Authentication and access control —Andrew Auernheimer The ability to designate roles, logins, and passwords is the most basic and most widely used level of (Charged in US Federal Court with database security.
    [Show full text]
  • The Gamma Database Machine Project
    The Gamma Database Machine Project David J. DeWitt Shahram Ghandeharizadeh Donovan Schneider Allan Bricker Hui-I Hsiao Rick Rasmussen Computer Sciences Department University of Wisconsin This research was partially supported by the Defense Advanced Research Projects Agency under contract N00039- 86-C-0578, by the National Science Foundation under grant DCR-8512862, by a DARPA/NASA sponsored Gradu- ate Research Assistantship in Parallel Processing, and by research grants from Intel Scientific Computers, Tandem Computers, and Digital Equipment Corporation. ABSTRACT This paper describes the design of the Gamma database machine and the techniques employed in its imple- mentation. Gamma is a relational database machine currently operating on an Intel iPSC/2 hypercube with 32 pro- cessors and 32 disk drives. Gamma employs three key technical ideas which enable the architecture to be scaled to 100s of processors. First, all relations are horizontally partitioned across multiple disk drives enabling relations to be scanned in parallel. Second, novel parallel algorithms based on hashing are used to implement the complex rela- tional operators such as join and aggregate functions. Third, dataflow scheduling techniques are used to coordinate multioperator queries. By using these techniques it is possible to control the execution of very complex queries with minimal coordination - a necessity for configurations involving a very large number of processors. In addition to describing the design of the Gamma software, a thorough performance evaluation of the iPSC/2 hypercube version of Gamma is also presented. In addition to measuring the effect of relation size and indices on the response time for selection, join, aggregation, and update queries, we also analyze the performance of Gamma relative to the number of processors employed when the sizes of the input relations are kept constant (speedup) and when the sizes of the input relations are increased proportionally to the number of processors (scaleup).
    [Show full text]
  • Security Guide for Oracle Exadata Database Machine
    Oracle® Exadata Database Machine Security Guide for Oracle Exadata Database Machine 21.2 F29252-09 September 2021 Oracle Exadata Database Machine Security Guide for Oracle Exadata Database Machine, 21.2 F29252-09 Copyright © 2008, 2021, Oracle and/or its affiliates. Primary Authors: Peter Fusek, Glenn Maxey Contributing Authors: Craig Brown, Dan Norris, James Spiller Contributors: Yang Liu, Philip Newlan, Tina Rose, Kevin Simmons, Zheren Zhang 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 embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • Foglight Performance Tuning Field Guide Updated - January 2018 Software Version - 5.9.2 Overview
    Foglight® 5.9.2 Performance Tuning Field Guide © 2018 Quest Software Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc. The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice.
    [Show full text]
  • Administering JDBC Data Sources for Oracle Weblogic Server 12C (12.2.1.2.0) E77969-03
    Oracle® Fusion Middleware Administering JDBC Data Sources for Oracle WebLogic Server 12c (12.2.1.2.0) E77969-03 December 2016 This book contains JDBC data source configuration and administration information. Oracle Fusion Middleware Administering JDBC Data Sources for Oracle WebLogic Server, 12c (12.2.1.2.0) E77969-03 Copyright © 2015, 2016, 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]
  • Cost/Benefit Case for IBM Db2 11.1 Compared to Oracle Database 12C for OLAP Deployments Sponsored By: IBM
    WHITEPAPER / JULY 14, 2017 / QL218356 Cost/Benefit Case for IBM Db2 11.1 Compared to Oracle Database 12c for OLAP Deployments Sponsored by: IBM Market Situation Today, organizations looking to grow their businesses have the opportunity to adopt innovative analytics applications to facilitate the process. New generation applications, coupled with modern database technologies and cutting-edge hardware, will enable organizations to rapidly generate actionable business insights to increase competitive advantage. At the same time, organizations must not only evaluate the performance of these business intelligence (BI) and analytics applications and the systems required to run them, but also their cost-effectiveness, compatibility with existing IT assets, capacity to meet growing organizational requirements, and ability to ensure business continuity. An increasing number of businesses are investing in cost-effective emerging technologies as a way to boost competitive advantage. However, despite the spotlight placed on BI and analytics offerings, the database foundation remains the crucial engine driving businesses processes and critical decision making for most organizations. A database platform that efficiently manages data and allows users to extract insights with ease will improve an organization’s efficiently and agility in confronting the challenges faced by modern businesses. IBM Db2, Oracle Database, MySQL, and Microsoft SQL Server continue to be dominant enterprise-ready databases, each supported by various hardware from established vendors. This paper presents a cost/benefit case for two industry-leading database platforms for analytics workloads—IBM Power Systems with AIX running IBM Db2 11.1 with BLU Acceleration, and Oracle Exadata Database Machine configured with Oracle Linux and Oracle Database 12c Release 2.
    [Show full text]
  • Risparmiare Consolidando Con Sun Oracle Database Machine
    <Insert Picture Here> Risparmiare consolidando con Sun Oracle Database Machine Alessandro Bracchini Sales Consulting – Oracle Italia Infrastruttura tradizionale: costosa ed inefficiente App A App B App C App D App E • Architettura a “Silos” lascia sottoutilizzate per diverso tempo le risorse Middleware HW disponibili Server 1 Server 2 Server 3 Server 4 Server 5 Scarso • utilizzo medio Alta Disponibilita’ ottenuta raddoppiando DB A DB B DB C DB D DB E risorse Server – Alti costi Database • Non ecologica: richiede piu’ elettricita’, spazio, Server 6 Server 7 Server 8 Server 9 Server 10 condizionamento, … Storage Consolidamento con il Grid Computing • E’ possibile far coesistere su risorse condivise virtuali Utilizzo medio Server carichi di lavoro Middleware Consolidated Apps A-E 75% Riutilizzabili complementari Server 1 Server 2 Server 3 Server 4 Server 5 • Si ottimizza il livello di utilizzo medio dei Server risparmiando Server sugli acquisti HW Database Cluster Database Riutilizzabili Utilizzo medio 70% ABCDE Server 6 Server 7 Server 8 Server 9 Server 10 • L’architettura e’ intrinsecamente affidabile Storage Storage Shared, Consolidated Storage Riutilizzabile • Maggiore efficienza = Green Computing Grid Computing Consolidamento e Virtualizzazione risorse IT •Dimensionati per picchi di carico •Gruppi di risorse condivise •Rigida •Ridistribuzione risorse se necessario •Complessa da gestire •Gestione centralizzata Best Machine for Consolidating Databases ● ERP Più database su uno stesso server ● Un unico storage per tutti i database CRM
    [Show full text]
  • Fortidb 5.1.13 Admin Guide 00-400-000000-20181031 TABLE of CONTENTS
    FortiDB - Admin Guide Version 5.1.13 FORTINET DOCUMENT LIBRARY https://docs.fortinet.com FORTINET VIDEO GUIDE https://video.fortinet.com FORTINET BLOG https://blog.fortinet.com CUSTOMER SERVICE & SUPPORT https://support.fortinet.com FORTINET TRAINING & CERTIFICATION PROGRAM https://www.fortinet.com/support-and-training/training.html NSE INSTITUTE https://training.fortinet.com FORTIGUARD CENTER https://fortiguard.com/ END USER LICENSE AGREEMENT https://www.fortinet.com/doc/legal/EULA.pdf FEEDBACK Email: [email protected] October 31, 2018 FortiDB 5.1.13 Admin Guide 00-400-000000-20181031 TABLE OF CONTENTS What’s new 11 Introduction 15 FortiDB tutorials 16 Tutorial: Generating a vulnerability assessment (VA) report 16 Tutorial: Monitoring a database table using the TCP/IP sniffer 19 Tutorial: Monitoring a database table using the native auditing feature 23 Tutorial: Monitoring changes to metadata 26 Tutorial: Generating PCI, SOX, and HIPAA compliance reports 28 Installation (software-only) 31 System requirements 31 Preparing to install 32 Configuring the FortiDB repository database 33 Configuring a PostgreSQL repository 33 Configuring an Oracle repository 34 Configuring an Microsoft SQL Server repository 35 UNIX/Linux installation 36 Windows installation 37 Confirming the installation 37 Starting or stopping FortiDB 38 Installing a new license 38 Managing disk space 39 Useful directories, files, and folders 39 Log files for troubleshooting 40 General logs 40 Tomcat logs 41 Upgrading FortiDB 41 How to set up your FortiDB 42 Registering your FortiDB 42 Planning the network topology for database activity monitoring (DAM) 42 Connecting to the web UI and CLI 43 Updating the firmware 43 Upgrading the firmware 44 Installing FortiDB firmware 45 Changing the "admin" account password 46 Setting the system time 47 Configuring the network settings 49 Configuring network settings using the web UI 49 Configuring network settings using the CLI 51 Backups 52 Administrators 53 Configuring permissions 54 FortiDB 5.1.13 Admin Guide 3 Fortinet Inc.
    [Show full text]
  • Datafeed Loader User Guide V2.10.1.0
    DataFeed Loader User Guide V2.10.1.0 Last Edited: August 2018 Table of Contents Updates ............................................................................................................................................................. 6 Overview ........................................................................................................................................................... 8 Product Offering ................................................................................................................................................ 8 Documentation ................................................................................................................................................. 8 Product Components ........................................................................................................................................ 8 Data Modeling .............................................................................................................................................. 8 Data Processing ............................................................................................................................................ 9 Data Integrity and Error Recovery ................................................................................................................. 9 Performance ................................................................................................................................................. 9 Disk Space ....................................................................................................................................................
    [Show full text]