DataWarehouse Dream Team
-
We are trying to re-build our data warehouse, also we want to move from SQL Server 2000 to 2005. Who should be on the team, I feel my current team missing some important people. Right now we don't have a data architect or data base designer, we don't have a dedicated DBA. I think these two people are very important on the team.
Also should the team leader have extensive data warehouse experience or it can rely on the data architect?
One of the biggest problem of re-writing a new data warehouse was there were many spagetti codes that someone had done long time ago and no one remembered why.
-
Sounds like you need a project manager. At least start with the Kimball DW Lifecycle book first. Given your spaghetti code comment I would start from scratch with Business user meetings and plenty of data analysis.
I am the DBA on a Data warehouse team but the team lead didn't think she needed to work with me before hiring a consultant. She did not put together or ask for scope documents or requirements and nobody seems able to tell me what the highest priority is. All the priorities fulfill executive expectations but do not ever address anyone else's. Although i am vocal she goes forward. Now... he has >knows< what the design should be after 2.5 weeks of evaluation - never see the data before. He also suggests what our "new" reporting tool should be although he has not once evaluated our existing report structure. I can't evaluate his ideas because he has produced no schema. He has fooled her into believing you don't need requirements before you design. He refuses to learn SSIS and he does all the etl (so he says) in old dts, linked servers and views. Since i won't allow the first two i will do all the SSIS grunt work. Hard to imagine but I have seen no evidence that he actually knows sql beyond a basic insert. He has asked me for a crib sheet of "all the business rules". I completely expect this project to take double the time and I will need to go back and at a minimum bandaid it. When I do explain that we can't do what they want it will be IT that is blamed.
-
That is the problem. My new manager does not think a DBA should involve in designing the data warehouse. He used to be a SQL developer involving in some ETL works (not data base designer) and he thinks he knows how to design a data warehouse. He has a template of everything which was his old work. He does not even write a SQL using the ANSII standard, which is no big deal but it shows that he does not get his technical skill up to date.
I looked at some of his codes which were terrible and no one could understand. But now he wants everyone of us following his standard.
I talked my old boss who becomes the director now, and he said it is my manager's project which he did not want to involve and he wanted my new manager take charge of everything.
I know the new data warehouse is going to be a piece of junk if he is in charge.
-
Ugg! that is even worse. my manager is at least in a agreement even if he is almost as stuck as I.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply