<?xml version="1.0" encoding="UTF-8"?>

<!-- <!DOCTYPE sddlschema SYSTEM "sddlschema.xsd">-->

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:  OPUS_RELEASE.SDDL -->
<!-- -->
<!--  Purpose:      This SDDL file defines the sogs_release relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       PR      Who                       Reason -->
<!--  - - - -    - - - -   - -    - - - - - - - - - - - - - - - - - - - - - -->
<!--  11/ 2/94   27329     EGB    Original implementation -->
<!--  01/15/96   30650     EGB    Reworked for OPUS / SPSS decoupling -->
<!--  12/21/99   40131.1   MARose Stolen from SPSS to create the opus version-->
<lm>  07/03/03   48821     CTB   Converted to XML format </lm> <!-- last mod -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->


    <record name="SOGSREL_TYPE">

        <description>This relation contains a history of OPUS database 
		   installations.  It is useful for determining the
                   build configuration of a SOGS compatible database.

		   This was needed to help maintain the proliferation 
		   of test databases - it was often difficult to determine 
		   what configuration they were in (i.e. what build they 
                   map to). 

		   The table is designed to have only a single record
		   in it at any one time so a simple select will be
		   able to tell you the database configuration level.

                   See original PR 26929 for more details, and PR
		   30650 for additional details.</description>


        <field name="opus_release_id">
                <type>C*10</type>
                <description>This field identifies tha latest OPUS release 
		     to update the SOGS database.

                     Sample values include:  10.3f, 5.0</description>
        </field>

        <field name="opus_install_date">
                <type>SYBASE_DATETIME</type>
                <description>This field is set to the time the current SOGS PMDB 
		     database was installed with OPUS-specific updates.</description>
        </field>

    </record>


    <relation name="opus_release">

        <type>SOGSREL_TYPE</type>

        <description>OPUS Project Management Database Identifier Relation</description>

        <subsystem_using>OPUS</subsystem_using>
        <subsystem_using>DBMS</subsystem_using>

        <index name="opus_release_1">
            <type>unique clustered</type>
            <field name="opus_release_id"/>
            <field name="opus_install_date"/>
        </index>

    </relation>

</sddl>
