David R. Shutt

Microsoft repository version 2 and the open information model

Abstract Microsoft Repository is an object-oriented meta-data management facility that ships in Microsoft Visual Studio and Microsoft SQL Server. It includes two main components: • • A repository engine that implements a set of object-oriented interfaces on top of a SQL database system. A developer can use these interfaces to define information models (i.e., schemas) and manipulate instances of the models. • • The Open Information Model, which is a set of information models that cover object modeling, database modeling, and component reuse. The repository system is designed to meet the persistent storage needs of software tools. Its main technical goals are: • • Compatibility with Microsofts Component Object Model (COM) architecture • • Extensibility by customers and independent software vendors, so they can add behavior to objects stored by the repository engine and extend information models provided by Microsoft and others. • • Flexible and efficient versioning, configuration management, and checkout/checkin to support team-oriented activities. This paper describes the programming interface and implementation of the repository engine and the Open Information Model.

Context-based prefetch – an optimization for implementing objects on relations

Abstract. When implementing persistent objects on a relational database, a major performance issue is prefetching data to minimize the number of round-trips to the database. This is especially hard with navigational applications, since future accesses are unpredictable. We propose the use of the context in which an object is loaded as a predictor of future accesses, where a context can be a stored collection of relationships, a query result, or a complex object. When an object Os state is loaded, similar state for other objects in Os context is prefetched. We present a design for maintaining context and for using it to guide prefetch. We give performance measurements of its implementation in Microsoft Repository, showing up to a 70% reduction in running time. We describe several variations of the optimization: selectively applying the technique based on application and database characteristics, using application-supplied performance hints, using concurrent database queries to support asynchronous prefetch, prefetching across relationship paths, and delayed prefetch to save database round-trips.

Versions and workspaces in Microsoft repository

This paper describes the version and workspace features of Microsoft Repository, a layer that implements fine-grained objects and relationships on top of Microsoft SQL Server. It supports branching and merging of versions, delta storage, checkout-checkin, and single-version views for version-unaware applications.