dwh_tutorial

Recommendations

Info

DWH These restrictions need to be considered carefully. Following are the points to remember: The process of encryption and decryption will increase overheads. It would require more processing power and processing time. The cost of encryption can be high if the system is already a loaded system because the encryption is borne by the source system. Data Movement There exist potential security implications while moving the data. Suppose we need to transfer some restricted data as a flat file to be loaded. When the data is loaded into the data warehouse, the following questions are raised: Where is the flat file stored? Who has access to that disk space? If we talk about the backup of these flat files, the following questions are raised: Do you backup encrypted or decrypted versions? Do these backups need to be made to special tapes that are stored separately? Who has access to these tapes? Some other forms of data movement like query result sets also need to be considered. The questions raised while creating the temporary table are as follows: Where is that temporary table to be held? How do you make such table visible? We should avoid the accidental flouting of security restrictions. If a user with access to the restricted data can generate accessible temporary tables, data can be visible to non-authorized users. We can overcome this problem by having a separate temporary area for users with access to restricted data. Documentation The audit and security requirements need to be properly documented. This will be treated as a part of justification. This document can contain all the information gathered from: Data classification User classification Network requirements 73
DWH Data movement and storage requirements All auditable actions Impact of Security on Design Security affects the application code and the development timescales. Security affects the following area: Application development Database design Testing Application Development Security affects the overall application development and it also affects the design of the important components of the data warehouse such as load manager, warehouse manager, and query manager. The load manager may require checking code to filter record and place them in different locations. More transformation rules may also be required to hide certain data. Also there may be requirements of extra metadata to handle any extra objects. To create and maintain extra views, the warehouse manager may require extra codes to enforce security. Extra checks may have to be coded into the data warehouse to prevent it from being fooled into moving data into a location where it should not be available. The query manager requires the changes to handle any access restrictions. The query manager will need to be aware of all extra views and aggregations. Database Design The database layout is also affected because when security measures are implemented, there is an increase in the number of views and tables. Adding security increases the size of the database and hence increases the complexity of the database design and management. It will also add complexity to the backup management and recovery plan. Testing Testing the data warehouse is a complex and lengthy process. Adding security to the data warehouse also affects the testing time complexity. It affects the testing in the following two ways: It will increase the time required for integration and system testing. There is added functionality to be tested which will increase the size of the testing suite. 74
Page 2 and 3:
About the Tutorial A data warehouse
Page 4 and 5:
IT Strategy .......................
Page 6 and 7:
Categories of Metadata ............
Page 8 and 9:
1. OVERVIEW DWH The term "Data Ware
Page 10 and 11:
DWH Data Warehouse Applications As
Page 12 and 13:
2. CONCEPTS DWH What is Data Wareho
Page 14 and 15:
DWH Data Transformation - Involv
Page 16 and 17:
DWH Data Cube A data cube helps us
Page 18 and 19:
DWH Data Mart Data marts contain a
Page 20 and 21:
4. DELIVERY PROCESS DWH A data ware
Page 22 and 23:
DWH and medium-term, then we can de
Page 24 and 25:
DWH The architecture is designed to
Page 26 and 27:
DWH Controlling the Process Control
Page 28 and 29:
6. ARCHITECTURE DWH In this chapter
Page 30 and 31: DWH Enterprise Warehouse Virtual W
Page 32 and 33: DWH The transformations affects
Page 34 and 35: DWH Detailed Information Detailed i
Page 36 and 37: 7. OLAP DWH Online Analytical Proce
Page 38 and 39: DWH Roll-up is performed by cl
Page 40 and 41: DWH Here Slice is performed for t
Page 42 and 43: DWH OLAP vs OLTP Data Warehouse (OL
Page 44 and 45: 8. RELATIONAL OLAP DWH Relational O
Page 46 and 47: 9. MULTIDIMENSIONAL OLAP DWH Multid
Page 48 and 49: 10. SCHEMAS DWH Schema is a logical
Page 50 and 51: DWH The sales fact table is sam
Page 52 and 53: DWH define dimension location as (l
Page 54 and 55: DWH Horizontal Partitioning There a
Page 56 and 57: DWH Round Robin Partitions In the r
Page 58 and 59: DWH Note: While using vertical part
Page 60 and 61: DWH Role of Metadata Metadata has a
Page 62 and 63: DWH Challenges for Metadata Managem
Page 64 and 65: DWH As the merchant is not interest
Page 66 and 67: DWH The summaries are data marted i
Page 68 and 69: 14. SYSTEM MANAGERS DWH System mana
Page 70 and 71: DWH Events Events are the actions t
Page 72 and 73: 15. PROCESS MANAGERS DWH Process ma
Page 74 and 75: DWH Functions of Warehouse Manager
Page 76 and 77: 16. SECURITY DWH The objective of a
Page 78 and 79: DWH But if each department accesses
Page 82 and 83: 17. BACKUP DWH A data warehouse is
Page 84 and 85: DWH Connecting the tape drive as
Page 86 and 87: DWH Will it work in cluster a
Page 88 and 89: DWH It is also essential that th
Page 90 and 91: DWH Points to Note It is important
Page 92 and 93: DWH Test Schedule First of all, the
Page 94 and 95: DWH Testing the Application All th
Page 96 and 97: 21. INTERVIEW QUESTIONS DWH Dear re
Page 98 and 99: DWH Q: Define a warehouse manager.
show all

dwh_tutorial

Create successful ePaper yourself

Delete template?

Save as template?