Abstract: In one embodiment, a data processing system includes a first database 304 maintained by a first party (such as a customer); a second database 324, 328 maintained by a second party (such as a vendor) different from the first party; a work queue 316 to specify data to be added to the second database; an extract, transform and load module 308 to write data from the first database to the work queue; and a data import module operable 320 to import data from the work queue to the second database. In the system, the first party is not privileged to write the data directly to the second database but is privileged to write the data to the work queue. The import module transforms the data written to the work queue to a form semantically compatible with the second database.

Abstract: A database architecture providing high availability and scalability is provided. According to embodiments of the present invention, multiple data sources are supported by multiple source databases. Partial copies of data stored in one or more of the source databases are provided to a consolidated database in response to requests for data received by the consolidated database from a data client. Multiple consolidated databases may support multiple data clients and data clients that are geographically dispersed. A sparse replication component operates to retrieve data from the source databases for storage in consolidated databases. The sparse data replication component can also monitor source databases for updates to requested data, and retrieve such data for storage in a consolidated database. In addition, each consolidated database may be associated with a data rationalization component to ensure that the data stored in the associated consolidated database does not include pathological data redundancies.

Abstract: In an information network of clients (101-102) and servers (103-104), a service management system (122) of a server gathers data from the server and from the clients for managing an information service. Information management data is gathered on a client by extensions (131) to a browser (130) and is periodically reported to the service management system. Data gathered on the server includes: number of page accesses per unit of time, durations of delays between receipt of client requests for information and the server responses thereto, number of accesses to each accessed page from each referring page, number of page accesses per browser type, processor and mass-storage occupancy of the server, and configuration details of each accessing browser.