Upgrading from Earlier Versions
A Microsoft® SQL Server™ 2000 Meta Data Services installation consists of certain core components, each of which can vary by version or format. A single configuration includes the following: a DBMS, a
- The DBMS used to manage the repository database can be Microsoft Jet 3.5 or later, SQL Server 6.5 or 7.0, or SQL Server 2000.
- The repository engine can be version 2.0 or 3.0.
- The repository database can be a 2.0 database or a 3.0 database (created with repository engine 2.0 or 3.0, respectively).
- Information models can be Microsoft Open Information Model (OIM) 1.0, Microsoft OIM 1.1, Meta Data Coalition (MDC) OIM, or a custom information model you define.
- XML interchange support can be XML Interchange Format (XIF) or the MDC XML Encoding format.
Recommended Configuration
We recommend that you upgrade to repository engine 3.0 on each computer, and that you upgrade your repository databases to the 3.0 format. In addition, you will get better performance and have access to more repository engine features if you migrate your repository database to SQL Server 2000.
Upgrading an information model provides access to more meta data types (for example, access to Unified Modeling Language (UML) 1.3 elements).
Whether you should upgrade your information models depends on the requirements of your tools and applications. For example, if your tools and applications are using Data Transformation Services (DTS) or Microsoft Visual Component Manager, it is not necessary to upgrade your information model. SQL Server 2000 and Visual Component Manager use the existing OIM as it is currently implemented.
Before upgrading an information model, you should determine whether a new model format will provide you with the definitions required for your repository applications. If a new model format does not offer compelling advantages, you should retain your existing information models for use with a 3.0 repository engine and databases.
For more information about upgrading any element of your Meta Data Services installation, see Retaining Legacy Components in a Repository.