>It is your job and you know the company and people involved. Would not be my style - esp. the part of "not raising the issue now, but may be later", as it already costs the company money and you are currently working on it.
>
>I am not into PC speak - but would hold you responsible as well if you were in the group of working on such a stink if brought in for a code review, perf optimization or to replace one of the higher ups. If ever questioned your only defense against collusion would be to argue own stupidity - not really a good long term strategy.

You're speaking from a purist point of view. There is an existing Code Base, lots of code written, several applications utilizing the particular database design. Could this design be made better? Absolutely. Is it cost effective to re-design now? Most likely not.

In any case, I am sure I am not the only one in our company knowing the shortcomings of the several of our tables. For the new development we're trying to use better practices. For the tables used in many applications already - I think our hands are currently tight up.