Hi mfarid2,
There is no way except convincing the higher officials what you have found.
This is the case at some of the places I worked. But, you need to understand the business very well, before you do any thing. Otherwise the blame will be on you. Please keep this in mind.
I have seen some places where the effective date and termdate not used at all properly (though they exist on tables) apart from no relationships and indexes.
Have a version control, so that you can have proper backups (also onto the tapes, in case any crashes).
Have the higher officials not to grant more than required privileges to any level.
Also, you have to have a design document how the process flow is done.
Document every thing you are doing.
All the best.
Main Topics
Browse All Topics





by: gmyersPosted on 2002-12-02 at 14:14:52ID: 7522224
"There are no primary keys on the tables and no indexes. No proper relationships. The same field is called with different names in different tables."
These are all 'technicalities' and there's no reason the 'business' should be interested in them.
Suggestions to the 'business' managers should be in business terms.
EG.
"I took a copy of the database.
I loaded up the June sales figures.
Then I loaded them up again, the sort of mistake that can easily be made if some-one goes off sick.
I then produced the financial projections and, see, we'd be buying an extra $100,000 of widgets if we used these forecasts.
We can put controls in place to make sure this can't happen."
or
"We can make changes that will get the December data out in time for the January report...without overtime"
Tell them how much the changes will cost to put in.
It may be the data(base) is so unimportant to them, they don't care.