Delivery Manager Tool - Extraction - Fatal Error - SQL T SQL MS - Unknown format id GROUP EXPORTER RESOLUTION ERROR IDENTIFICATION GROUP VALUE

This page provides solution to the error (mentioned below) encountered while running SQL Server extraction for SQL Server 2000 in DMT.

 INFO Extracting: MS SQL Server Database...
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_Database" %IDENTIFICATION%="p_Instance" %VALUE%="default"
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_Database" %IDENTIFICATION%="p_Instance" %VALUE%="default"

 INFO Extracting: MS SQL Server Tables...
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_RelationalTable" %IDENTIFICATION%="p_Schema" %VALUE%="dbo"
 INFO 1 MS SQL Server Tables rows extracted in 359 ms [rate: 2 rows/s]

 INFO Extracting: MS TSQL foreign key constraints on tables...
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_ForeignKeyConstraint" %IDENTIFICATION%="VASTCreateTable" %VALUE%="PHBweb_Test.dbo.Addendum"
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_ForeignKeyConstraint" %IDENTIFICATION%="VASTCreateTable" %VALUE%="PHBweb_Test.dbo.Addendum"
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_ForeignKeyConstraint" %IDENTIFICATION%="VASTCreateTable" %VALUE%="PHBweb_Test.dbo.Addendum_Rebaseline"

 INFO Extracting: MS TSQL user primary key constraints on tables...
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_PrimaryKeyConstraint" %IDENTIFICATION%="VASTCreateTable" %VALUE%="PHBweb_Test.dbo.Activity"
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_PrimaryKeyConstraint" %IDENTIFICATION%="VASTCreateTable" %VALUE%="PHBweb_Test.dbo.Addendum"
 INFO Unkown format id: GROUP_EXPORTER_RESOLUTION_ERROR_IDENTIFICATION_GROUP_VALUE => %TYPE%="CAST_MSTSQL_PrimaryKeyConstraint" %IDENTIFICATION%="VASTCreateTable" %VALUE%="PHBweb_Test.dbo.Addendum_Rebaseline"

1.  Open the DMT.
2.  Add a package for database of type MS SQL SERVER and select CAST Extractor for MS option.
3.  Entered the login credentials (Host name, port number etc.).
4.  Try to package and will get the error.

This error is encountered because, the queries in the config file for SQL Server 2000 are not correct. As a result of this the database and its objects are not extracted completely.

So, to fix this issue, there is a workaround, which you can apply as mentioned below:

1. You can migrate your SQL server 2000 DB's to SQL server 2005/2008 (recent updates) and then do the extraction using DMT and you will no longer get the errors resulting in incomplete extraction.
   1. Backup database from SQL server 2000.
   2. Restore the DB backup in SQL server 2005/2008 (Same collation as SQL server 2000).
   3. Set the compatibility of this SQL server 2000 DB to SQL server 2005/2008.

   4. See the below sample syntax on how to set compatibility, depending on the version you would be migrating to.
      Syntax: ALTER DATABASE database_name SET COMPATIBILITY_LEVEL = { 130 | 120 | 110 | 100 | 90 }

      • database_name Is the name of the database to be modified.
      • COMPATIBILITY_LEVEL { 130 | 120 | 110 | 100 | 90 | 80 } Is the version of SQL Server with which the database is to be made compatible. The following compatibility level values can be configured:

      Product	Database Engine Version	Compatibility Level Designation	Supported Compatibility Level Values
      SQL Server 2016 Release Candidate (RC3)	13	130	130, 120, 110, 100
      SQL Database	12	120	130, 120, 110, 100
      SQL Server 2014	12	120	120, 110, 100
      SQL Server 2012	11	110	110, 100, 90
      SQL Server 2008 R2	10.5	105	100, 90, 80
      SQL Server 2008	10	100	100, 90, 80
      SQL Server 2005	9	90	90, 80
      SQL Server 2000	8	80	80

   5. Connect and run the extraction from DMT. 

Impact of error : Extraction is not successful

Impact of solution : Extraction is successful