Database Schema Archive

Run CM4DSITE_020_FROM_O10_UPDATE.sql to get to schema 20 [Continue to next update]

With SQL Server, you may receive the following messages. These messages are expected and do not indicate a problem.
   Server: Msg 2627, Level 14, State 1, Line 1
   Violation of PRIMARY KEY constraint 'PK_GroupID'.
   Cannot insert duplicate key in object 'GroupID'.
   The statement has been terminated.
   Server: Msg 2627, Level 14, State 1, Line 1
   Violation of PRIMARY KEY constraint 'PK_GroupUser'.
   Cannot insert duplicate key in object 'GroupUser'.
   The statement has been terminated.
   Server: Msg 2627, Level 14, State 1, Line 1
   Violation of PRIMARY KEY constraint 'PK_GroupPrivilege'.
   Cannot insert duplicate key in object 'GroupPrivilege'.
   The statement has been terminated.

Run CM4DSITE_021_UPDATE.sql to get to schema 21 [Continue to next update]

Run CM4DSITE_021_UPDATE_FROM_012.sql to get to schema 21 [Continue to next update]

Run CM4DSITE_021_UPDATE.sql to get to schema 21 [Continue to next update]

Run CM4DSITE_022_UPDATE.sql to get to schema 22 [Continue to next update]

With SQL Server, you may receive the following messages. These messages are expected and do not indicate a problem.
   Caution: Changing any part of an object name could break scripts and stored procedures.
   The object was renamed to 'SCHEDULESETTINGOLD'.
   Caution: Changing any part of an object name could break scripts and stored procedures.
   The object was renamed to 'PK_SCHEDULESETTINGOLD'.

Run SITE UPDATE 23.sql to get to schema 23 [Continue to next update]

Run SITE UPDATE 24.sql to get to schema 24 [Continue to next update]

Run SITE UPDATE 25.sql to get to schema 25 [Continue to next update]

Run UpdateSite26.sql to get to schema 26 [Continue to next update]

Run UpdateSite27.sql to get to schema 27 [Continue to next update]

Run UpdateSite28.sql to get to schema 28 [Continue to next update]

Run UpdateSite29.sql to get to schema 29 [Continue to next update]

Run UpdateSite30.sql to get to schema 30 [Continue to next update]

Run UpdateSite12a.sql to get to schema 12a [Continue to next update]

CM4D Databases

Run CM4D_017_UPDATE.sql to get to schema 17 [Continue to next update]

Run CM4D_018_UPDATE.sql to get to schema 18 [Continue to next update]

With SQL Server, you may receive one or more messages. These messages are expected and do not indicate a problem.
Cannot drop the procedure 'abc', because it does not exist in the system catalog.

Run CM4D_019_UPDATE.sql to get to schema 19 [Continue to next update]

1. Run CM4D_025_UPDATE.sql to schema 25

With SQL Server, you may receive the following messages. These messages are expected and do not indicate a problem.
   Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'FEATVARLIMITOLD'.
    Server: Msg 15225, Level 11, State 1, Procedure sp_rename, Line 273
    No item by the name of 'PK_FEATVARLIMIT' could be found in the current database 'abc', given that @itemtype was input as '(null)'.
    Server: Msg 3703, Level 11, State 7, Line 4
    Cannot drop the index 'FEATVARLIMIT.CM4D_FEATVARLIMIT_FVL_R_ID', because it does not exist in the system catalog.

2. Run DataMigrator.exe to migrate the schema 25 data [Continue to next update]

If you are migrating a managed datasource, make sure the cm4d.ini file is referencing the Site where the datasource is managed. You do not need to specify the destination, but if no destination is provided, the source will be used as the destination and an in-place migration will be performed. Not specifying a destination is the recommended migration method.

Run CM4D_027_UPDATE.sql to schema 27 [Continue to next update]

With Oracle, you may receive the following messages. These messages do not indicate a problem.
Failed to delete Object that does not exist
With SQL Server, you may receive the following messages. These messages are expected and do not indicate a problem.
   Server: Msg 3701, Level 11, State 5, Line 10
    Cannot drop the table 'ROUTINEOLD', because it does not exist in the system catalog.
    Server: Msg 3701, Level 11, State 5, Line 11
    Cannot drop the table 'FEATVARLIMITOLD', because it does not exist in the system catalog.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'FEATVARLIMITOLD'.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'ROUTINEOLD'.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'PK_FEATVARLIMITOLD'.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'PK_ROUTINEOLD'.

Run UPDATE 28.sql to schema 28 [Continue to next update]

Run UPDATE 29.sql to schema 29 [Continue to next update]

With SQL Server, you may receive the following messages. These messages are expected and do not indicate a problem.
   Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'ACTUALOLD29'.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'PK_ACTUALOLD29'.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'FEATVARLIMITOLD29'.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    The object was renamed to 'PK_FEATVARLIMITOLD29'.

Run UPDATE 30.sql to schema 30 [Continue to next update]

Run Update31.sql to schema 31 [Continue to next update]

With Oracle, you may receive warning messages when three obsolete stored procedures are deleted. These messages are expected and do not indicate a problem. The obsolete procedures are:
    CreateArchiveSampleList
    LoadArchiveStatus
    UpdateArchiveStatus

Run Update32.sql to schema 32 [Continue to next update]

Run Update33.sql to schema 33 [Continue to next update]

Run Update34.sql to schema 34 [Continue to next update]

Run Update35.sql to schema 35 [Continue to next update]

Run Update12a.sql to schema 12a [Continue to next update]

CM4D Archive Versions and Schemas

The following table provides a cross-reference of the CM4D versions in which each database Schema was introduced. The scripts listed apply for both Oracle and SQL Server (unless otherwise indicated).

CM4D Version	Site Schema	Update Site Script		CM4D Schema	Update CM4D Script
v10.610	10	SITE UPDATE 10.sql		17	UPDATE 17.SQL
v10.700	11 or 20	SITE UPDATE 20 FROM 10.SQL		18	UPDATE 18.SQL
v10.705	20			19	UPDATE 19.SQL
v10.720*	12	SQL	20	19
v10.720*	12	ORA	SITE UPDATE 12.sql	19
v10.750	21			25	UPDATE 25.SQL
v10.761	21	SQL	SITE UPDATE 21.SQL	25
v10.761	21	ORA	SITE UPDATE 21.SQL SITE UPDATE 21 FROM 12.sql	25
v10.795	21			26	UPDATE 26.SQL
v10.810	21			27	UPDATE 27.SQL
v10.825	22	SITE UPDATE 22.SQL		27
v10.861	23	SITE UPDATE 23.SQL		28	UPDATE 28.SQL
v10.900	24	SITE UPDATE 24.sql		29	UPDATE 29.SQL
v10.910	25	SITE UPDATE 25.sql		30	UPDATE 30.SQL
v10.952	26	UpdateSite26.sql		31	Update31.sql
v10.977	27	UpdateSite27.sql		31
v11.1.1	28	UpdateSite28.sql		32	Update32.sql
v11.2.1	28			33	Update33.sql
v11.3.1	29	UpdateSite29.sql		34	Update34.sql
v11.3.3	30	UpdateSite30.sql		34
v11.3.4	30			35	Update35.sql
v11.4.1	31	UpdateSite31.sql		36	Update36.sql