Database Security 5. Backup and Recovery 6. Data Integrity

Database Administrator (DBA) The Database Administrator is a man responsible for the • Installation • Configuration • Upgradation • Administration • Monitoring and upkeep of databases Fundamental Roles: 1. Database arrangement 2. Database transparency 3. Performance issues 4. Capacity issues 5. Data Replication 6. Table upkeep DBA Functional Organization: 1. Planning 2. Design a) Conceptual b) Logical 3. Implementation a) Physical b) Testing 4. Operations 5. Training DBA Tasks: 1. Database arrangement 2. Performance checking and tuning 3. Database openness 4. Security 5. Backup and Recovery 6. Data Integrity 7. Release Migration Data Warehouse Administrator Data stockroom: • It is a stay lone store of information, facilitated from a couple, possibly heterogeneous operational databases. • It is a strategy, not a thing. Data stockroom administrator parts: • New part, going with the advancement in data stockrooms • Similar to DBA/DA parts • Specific parts: 1) Support DSS applications 2) Manage data stockroom advancement 3) Establish organization level assentions regarding data circulation focuses and data stores • Tasks: 1) Involved in KPI (Key, Performance, Indicator) ? The KPI has a) Measure b) Innovate c) Propagate d) Strategize Connection between’s DBA && DWA Characteristics Data Warehouse Database Workload Designed to oblige off the cuff request. You may not know the workload of your data circulation focus early, so it should be progressed to perform well for a wide arrangement of possible queries. Supports just predefined operations. Your applications might be especially tuned or expected to help only these operations. Data modifications Updated all the time by the ETL technique using mass data alteration strategies. End customers of a data conveyance focus don’t direct invigorate the database. Subject to individual DML enunciations routinely issued by end customers. The OLTP database is constantly excellent and mirrors the current state of each business trade. Development design Uses de-institutionalized or for the most part de-institutionalized mappings, (for instance, a star design) to update request performance. Uses totally institutionalized outlines to improve DML execution and to guarantee data consistency. Common operations A regular inquiry checks thousands or a considerable number of sections. For example, a customer may request the total arrangements for all customers last month. A average operation gets to only an unassuming pack of records. For example, a customer may recuperate the present demand for a singular customer. Recorded data Stores various months or years of data to help bona fide analysis. Stores data from simply a large portion of a month or months. Undeniable data held of course to meet the necessities of the present trade.