| This scenario is pretty common. I am an engineer, not a programmer, but I got stuck with our billing database at my last company (~50 employees, $11mil/yr revenue). It was written in Access, bloated, and slow as molasses.
The company I work at now has ~1000 employees, ~500mil/yr revenue, and uses PeopleSoft (on MSSQL server). They must have a team of at least 10 contractors who work on it. Costs a goddamn fortune (millions per year) and is less user friendly than the Access database. We need cheat sheets to fill out expenses.
My neighbor is a DBA for the cable company here (Time Warner). Based on discussions with him and my past 2 jobs, I don't think most people in charge of their company's databases understand normalization and proper database design. There is just not enough talent to meet the demand, so a lot of people just get thrown at it because they are good with computers.
Anyway, shoot your questions on here and I can try my best to answer them. I am no DBA but I have a decent grasp of design.
__________________
If God didn't want us to eat animals, why did He make them out of meat?
Last edited by Phelps McManus : 04-04-2008 at 07:41 PM.
|