×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Data Warehouse Change Control

Data Warehouse Change Control

Data Warehouse Change Control

(OP)
I am getting ready to turn a Data Warehouse project over to production. With a "production" system comes the baggage of Change Control. Our DW architecture allows users to create their own temporary tables within the DW and join those tables with the "production warehouse tables". How should such modifications to the DW be handled from a change control perspective? How are DW changes in general handled from a change control perspective?

RE: Data Warehouse Change Control

Whether you permit end users to create tables on the data warehouse or they export the data to some other platform for further processing, the impact is the same, with one exception. Over time, some of these user tables will tend to become "permanent". Users other than the ones who created them will come to depend on them. This will eventually lead to the same evils that your warehouse was created to remedy, inconsistancy and lack of documentation being at the head of the list. This is not a quantifiable risk. It is an absolute certainty. One way to head this off is to restrict access to these tables to the users who create them, unless you mean that these tables are literally temporary tables and will not survive the session during which they are created. I suspect from the way you framed your question that this is not the case. I assume you mean that certain "power" users will have "create" privileges. If this is the case, beware. Before too long, you, or the production staff charged with maintaining the warehouse, will be presented with a request to make a user table public. This will almost certainly put you in the position of rubber stamping a modification you know will have adverse consequences or criticizing the analytical skills of your client. This is also known as being between a rock and a hard place. Try not to go there.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close