Answer:
Both the ETL packages and the cube definitions for the solution should be under Source control using Check-in and Check-out to ensure a well defined baseline for both production and test versions. New test versions are deployed to the test copy of the data warehouse and cubes and tested on a backup from the production data. Only authorized and tested versions of the ETL and Cubes are deployed to the production servers.
A database schema comparison tool is used to carefully manage and deploy any schema changes from test to production. Portal changes to reports and dashboards are managed by the content control features of the portal that supports testing of the published version but it is not visible to the users until the portal administrator authorizes the new content version.
| |
|
|
