1. DATABASE 1 Data Administration  Data and information are valuable assets.  Data is used at many business levels  Operations and transactions.  Tactical management.  Strategic management.  There are many databases and applications in an organization.  Someone has to be responsible for organizing, controlling, and sharing data.  Data Administrator (DA) Business Operations Tactical Management Strategic Management EIS ES DSS Transaction Processing Process Control

2. DATABASE 2 Data Administrator (DA)  Provide centralized control over the data.  Data definition. Format Naming convention  Data integration.  Selection of DBMS.  Act as data and database advocate.  Application ideas.  Decision support.  Strategic uses.  Coordinate data integrity, security, and control.

3. DATABASE 3 Database Administrator (DBA)  Install and upgrade DBMS.  Create user accounts and monitor security.  In charge of backup and recovery of the database.  Monitor and tune the database performance.  Coordinate with DBMS vendor and plan for changes.  Maintain DBMS-specific information for developers.

4. DATABASE 4 DBA Tools: Oracle Schema Manager

5. DATABASE 5 DBA Tools: SQL Server Enterprise Mgr.

6. DATABASE 6 Microsoft Access

7. DATABASE 7 DBA Tools: Performance Monitors

8. DATABASE 8 Microsoft Access: Analyze Performance Tools Analyze Performance

9. DATABASE 9 SQL Server Query Analyzer

10. DATABASE 10 SQL Query Analyzer Detail

11. DATABASE 11 Oracle Query Analysis ALTER SYSTEM SET TIMED_STATISTICS=true; ALTER SYSTEM SET USER_DUMP_DEST= ‘newdir’; ALTER SESSION SET SQL_TRACE = true; Run your query ALTER SESSION SET SQL_TRACE = false; EXPLAIN PLAN SET STATEMENT_ID = ‘Your title’ INTO output FOR Your query Requires output table be setup first.

12. DATABASE 12 Oracle SQL Trace call count cpu elapsed disk query current rows ----- ------ ----- ------- ----- ----- ------- ---- Parse 1 0.02 0.04 0 0 0 0 Execute 1 0.00 0.00 0 0 0 0 Fetch 12 0.00 0.00 0 823 4 164 ----- ------ ----- ------- ----- ----- ------- ---- total 14 0.02 0.04 0 823 4 164 Misses in library cache during parse: 1 Optimizer goal: CHOOSE Parsing user id: 26 Rows Row Source Operation ------- --------------------------------------------- 164 NESTED LOOPS 303 NESTED LOOPS 197 TABLE ACCESS FULL SALE 498 INDEX RANGE SCAN (object id 3398) 164 TABLE ACCESS BY INDEX ROWID MERCHANDISE 604 INDEX UNIQUE SCAN (object id 3388)

13. DATABASE 13 Database Administration  Planning  Determine hardware and software needs.  Design  Estimate space requirements, estimate performance.  Implementation  Install software, create databases, transfer data.  Operation  Monitor performance, backup and recovery.  Growth and Change  Monitor and forecast storage needs.  Security  Create user accounts, monitor changes.

14. DATABASE 14 Database Planning  Estimation  Data storage requirements  Time to develop  Cost to develop  Operations costs

15. DATABASE 15 Managing Database Design  Teamwork  Data standards  Data repository  Reusable objects  CASE tools  Networks / communication  Subdividing projects  Delivering in stages User needs / priorities Version upgrades  Normalization by user views Distribute individual sections Combine sections  Assign forms and reports

16. DATABASE 16 Database Implementation  Standards for application programming.  User interface.  Programming standards. Layout and techniques. Variable & object definition.  Test procedures.  Data access and ownership.  Loading databases.  Backup and recovery plans.  User and operator training.

17. DATABASE 17 Database Operation and Maintenance  Monitoring usage  Size and growth  Performance / delays  Security logs  User problems  Backup and recovery  User support  Help desk  Training classes

18. DATABASE 18 Database Growth and Change  Detect need for change  Size and speed  Structures / design Requests for additional data. Difficulties with queries.  Usage patterns  Forecasts  Delays in implementing changes  Time to recognize needs.  Time to get agreement and approval.  Time to install new hardware.  Time to create / modify software.

19. DATABASE 19 Backup and Recovery  Backups are crucial!  Offsite storage!  Scheduled backup.  Regular intervals.  Record time.  Track backups.  Journals / logs  Checkpoint  Rollback / Roll forward OrdIDOdateAmount... 1922/2/01252.35… 1932/2/01 998.34… OrdIDOdateAmount... 1922/2/01 252.35… 1932/2/01 998.34… 1942/2/01 77.23... OrdIDOdateAmount... 1922/2/01252.35… 1932/2/01998.34… 1942/2/0177.23… 1952/2/01101.52… Snapshot Changes Journal/Log

20. DATABASE 20 Database Security and Privacy  Physical security  Protecting hardware  Protecting software and data.  Logical security  Unauthorized disclosure  Unauthorized modification  Unauthorized withholding  Security Threats  Employees / Insiders Disgruntled employees “Terminated” employees Dial-up / home access  Programmers Time bombs Trap doors  Visitors  Consultants  Business partnerships Strategic sharing EDI  Hackers--Internet

21. DATABASE 21 Data Privacy Who owns data? Customer rights. International complications. Do not release data to others. Do not read data unnecessarily. Report all infractions and problems.

22. DATABASE 22 Physical Security  Hardware  Preventing problems Fire prevention Site considerations Building design  Hardware backup facilities Continuous backup (mirror sites) Hot sites Shell sites “Sister” agreements  Telecommunication systems  Personal computers  Data and software  Backups  Off-site backups  Personal computers Policies and procedures Network backup  Disaster planning  Write it down  Train all new employees  Test it once a year  Telecommunications  Allowable time between disaster and business survival limits.

23. DATABASE 23 Physical Security Provisions  Backup data.  Backup hardware.  Disaster planning and testing.  Prevention.  Location.  Fire monitoring and control.  Control physical access.

24. DATABASE 24 Managerial Controls  “Insiders”  Hiring  Termination  Monitoring  Job segmentation  Physical access limitations Locks Guards and video monitoring Badges and tracking  Consultants and Business alliances  Limited data access  Limited physical access  Paired with employees

25. DATABASE 25 Logical Security  Unauthorized disclosure.  Unauthorized modification.  Unauthorized withholding.  Disclosure example  Letting a competitor see the strategic marketing plans.  Modification example  Letting employees change their salary numbers.  Withholding example  Preventing a finance officer from retrieving data needed to get a bank loan.

26. DATABASE 26 User Identification  User identification  Accounts  Individual  Groups  Passwords  Do not use “real” words.  Do not use personal (or pet) names.  Include non-alphabetic characters.  Use at least 6 (8) characters.  Change it often.  Too many passwords!  Alternative identification  Finger / hand print readers  Voice  Retina (blood vessel) scans  DNA typing  Hardware passwords  The one-minute password.  Card matched to computer.  Best method for open networks / Internet.

27. DATABASE 27 Basic Security Ideas  Limit access to hardware  Physical locks.  Video monitoring.  Fire and environment monitors.  Employee logs / cards.  Dial-back modems  Monitor usage  Hardware logs.  Access from network nodes.  Software and data usage.  Background checks  Employees  Consultants phone company phone company 1 4 5 2 3 Jones 1111 Smith 2222 Olsen 3333 Araha 4444  Dialback modem  User calls modem  Modem gets name, password  Modem hangs up phone  Modem calls back user  Machine gets final password

28. DATABASE 28 Access Controls  Operating system  Access to directories Read View / File scan Write Create Delete  Access to files Read Write Edit Delete  DBMS usually needs most of these  Assign by user or group.  DBMS access controls  Read Data  Update Data  Insert Data  Delete Data  Open / Run  Read Design  Modify Design  Administer  Owners and administrator  Need separate user identification / login to DBMS.

29. DATABASE 29 SQL Security Commands  GRANT privileges  REVOKE privileges  Privileges include  SELECT  DELETE  INSERT  UPDATE  Objects include  Table  Table columns (SQL 92+)  Query  Users include  Name/Group  PUBLIC GRANT INSERT ON Bicycle TO OrderClerks REVOKE DELETE ON Customer FROM Assemblers

30. DATABASE 30 Oracle Security Manager

31. DATABASE 31 SQL Server Security Manager

32. DATABASE 32 Using Queries for Control  Permissions apply to entire table or query.  Use query to grant access to part of a table.  Example  Employee table  Give all employees read access to name and phone (phonebook).  Give managers read access to salary.  SQL  Grant  Revoke Employee(ID, Name, Phone, Salary) Query: Phonebook SELECT Name, Phone FROM Employee Security Grant Read access to Phonebook for group of Employees. Grant Read access to Employee for group of Managers. Revoke all access to Employee for everyone else (except Admin).

33. DATABASE 33 Separation of Duties SupplierIDName… 673Acme Supply 772Basic Tools 983Common X Supplier OrderIDSupplierID 8882772 8893673 8895009 PurchaseOrder Referential integrity Clerk must use SupplierID from the Supplier table, and cannot add a new supplier. Purchasing manager can add new suppliers, but cannot add new orders.

34. DATABASE 34 Securing an Access Database  Set up a secure workgroup  Create a new Admin user.  Enable security by setting a password  Remove the original Admin user.  Run the Security Wizard in the database to be secured.  Assign user and group access privileges in the new database.  Encrypt the new database.  Save it as an MDE file.

35. DATABASE 35 Encryption  Protection for open transmissions  Networks  The Internet  Weak operating systems  Single key  Dual key  Protection  Authentication  Trap doors / escrow keys  U.S. export limits  64 bit key limit  Breakable by brute force Typical hardware:2 weeks Special hardware: minutes Plain text message Encrypted text Key: 9837362 DES Encrypted text Plain text message DES Single key: e.g., DES

36. DATABASE 36 Dual Key Encryption  Using Takao’s private key ensures it came from him.  Using Makiko’s public key means only she can read it. Makiko Takao Public Keys Makiko 29 Takao 17 Private Key 13 Private Key 37 Use Takao’s Public key Use Takao’s Private key Message Encrypt+T Encrypt+T+M Encrypt+M Use Makiko’s Public key Use Makiko’s Private key Transmission

37. DATABASE 37 Sally’s Pet Store: Security Management Sally/CEO Sales Staff Store manager Sales people Business Alliances Accountant Attorney Suppliers Customers Products Sales Purchases Receive products Animals Sales Purchases Animal Healthcare Employees Hiring/Release Hours Pay checks Accounts Payments Receipts Management Reports Users Operations

38. DATABASE 38 Sally’s Pet Store: Purchases *Basic Supplier data: ID, Name, Address, Phone, ZipCode, CityID R:Read W:Write A:Add