Scribd
Upload
8 views16 pages

Lecture 4 (A B)

Uploaded by

saadcoder12
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
8 views16 pages

Lecture 4 (A B)

Uploaded by

saadcoder12
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 16

Data and Database

Administration
By
Lec. Adeel Shahzad
From
Book-B

1
Traditional Administration Definitions
• Data Administration: A high-level function that is
responsible for the overall management of data
resources in an organization, including maintaining
corporate-wide definitions and standards
• Database Administration: A technical function that is
responsible for physical database design and for
dealing with technical issues such as security
enforcement, database performance, and backup
and recovery

2
Traditional Data Administration
Functions
• Data policies, procedures, standards
• Planning
• Data conflict (ownership) resolution
• Managing the information repository
• Internal marketing of DA concepts

3
Traditional Database
Administration Functions
• Selection of DBMS and software tools
• Installing/upgrading DBMS
• Tuning database performance
• Improving query processing performance
• Managing data security, privacy, and integrity
• Data backup and recovery

4
Evolving Approaches to Data
Administration
• Blend data and database administration into one role
• Fast-track development–monitoring development process
(planning, analysis, design, implementation, maintenance)
• Procedural DBAs–managing quality of triggers and stored
procedures
• eDBA–managing Internet-enabled database applications
• PDA DBA–data synchronization and personal database
management
• Data warehouse administration

5
Open Source DBMSs
• An alternative to proprietary packages such as Oracle,
Microsoft SQL Server, or Microsoft Access
• mySQL is an example of an open-source DBMS
• Less expensive than proprietary packages
• Source code available, for modification
• Absence of complete documentation
• Ambiguous licensing concerns
• Not as feature-rich as proprietary DBMSs
• Vendors may not have certification programs

6
Figure 13-2 Data modeling responsibilities

7
Database Security
• Database Security: Protection of the
data against accidental or intentional
loss, destruction, or misuse
• Increased difficulty due to Internet
access and client/server technologies

8
Figure 13-3 Possible locations of data security threats

9
Threats to Data Security
• Accidental losses attributable to:
– Human error
– Software failure
– Hardware failure
• Theft and fraud
• Improper data access:
– Loss of privacy (personal data)
– Loss of confidentiality (corporate data)
• Loss of data integrity
• Loss of availability (through, e.g. sabotage)

10
Figure 13-4 Establishing Internet Security

11
Web Security
• Static HTML files are easy to secure
– Standard database access controls
– Place Web files in protected directories on server
• Dynamic pages are harder
– Control of CGI scripts
– User authentication
– Session security
– SSL for encryption
– Restrict number of users and open ports
– Remove unnecessary programs

12
Database Software Security
Features
• Views or subschemas
• Integrity controls(Accuracy, Completeness, Consistency)
• Authorization rules
• User-defined procedures
• Encryption
• Authentication schemes
• Backup, journalizing, and checkpointing

13
Database Recovery
 Mechanism for restoring a database quickly
and accurately after loss or damage
 Recovery facilities:
• Backup Facilities
• Journalizing Facilities
• Checkpoint Facility
• Recovery Manager

14
Back-up Facilities
• Automatic dump facility that produces
backup copy of the entire database
• Periodic backup (e.g. nightly, weekly)
• Cold backup–database is shut down during
backup
• Hot backup–selected portion is shut down
and backed up at a given time
• Backups stored in secure, off-site location

15
Checkpoint Facilities
• DBMS periodically refuses to accept new
transactions
•  system is in a quiet state
• Database and transaction logs are
synchronized

This allows recovery manager to resume


processing from short period, instead of
repeating entire day
16

You might also like