One of our Challengers would like our advice. Here is a summary of his challenge:

"Occasionally a battle erupts in our department between the application architects and the data architects. For example, the AAs want to remove database referential integrity so that programming or data movement will be easier. As DAs, we attempt to convince them that this may be a good short-term plan but will be bad for the long-term integrity of the data, which should be at the forefront of our data design decisions. If we are deadlocked in battle, upper management becomes involved to break the tie. More often than not, they side with the AAs. We think this is because the managers understand application functionality much better than they understand data architecture. What steps can we take so that we will start winning more battles?"

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access