6. November 2008 00:04
Far too often in large organizations there is a disconnect between different DBAs, IT staff and application developers. I think what would be a good thing to see in increasing use would be a small handful of people that understand the mapping of various database schemas for applications within a large organization, and provide a common database interface.
With the release of the ADO.Net Data Services Framework (formerly Astoria), I think this could be a great bridge for such a beast. Simply offering a consistant set of endpoints for data services, for use with servers within an organization, with traffic restricted is much better in my opinion than having numerous web services exposing data from one system to another. A single interface, with a healthy redundancy that is, not to be confused with a single point of failure. Even if actual service end points within a common interface point to various legacy systems, and webservices, it makes a decent system moving forward.
The hard part is making progress, while maintaining communications with many different teams and departments. Such a Data Czar would have to have enough people to actually develop and maintain common interfaces, keeping communications with DBAs and IT staff in order to organize changes, as well as respond quickly to developer requests which will include scenarios that may not make it to production, and keeping track of changes that will ultimately be scrapped. Not to mention protecting sensitive information from being directly viewable.