Database Design and Security
If added security increases the number of database objects, such as tables and views, this will affect the database layout. Remember that each copy or version of a table can mean many more objects in the database. For example, if a table has three indexes, three constraints, and five views on it, each copy of the table will probably add not just the copy but 11 other objects to the database as well. If enforcing the security adds to the size of the database, it automatically adds to the complexity of the database management and the backup recovery plan. This may affect your database design, particularly if you are already close to the limit of your database size, machine capacity or backup times within the overnight window.
The testing of the design of a data warehouse is a complex and lengthy process. When further security is added to the task it increases the test time in two ways. First, the added complexity of the programs to be tested will increase the time required for integration and system testing. The added complexity will most likely increase the number of errors found in testing and the amount of recoding that needs to be performed. Second, there is added functionality to be tested: this will increase the size of the test suite. This means that the testing will take longer to plan and develop, which in turn will increase the amount of time taken for testing.