SQL 6.5 to 2000 upgrade problems

  • Guess I am the lucky one. When I try to upgrade (same server- took a ghost copy of original for test box and renamed NT and SQL names) a SQL 6.5 box to SQL 2000, I am losing all data in some of the tables. In 6.5, they were fine. In 2000, blank.

    An example is the Ticket table (here is the error report file):

    Export Exit Code: -2147467259 - c:\progra~1\micros~1\mssql\upgrade\export.exe -CodePage 850 -DeviceType Pipe -AllTables yes -MasterPath D:\SQL\DATA\MASTER.DAT -DatabaseName WINLANCE -DevicePath \\.\pipe\~cnvpipe1

    An error occured while importing table. Please check the error file.

    Time : 01-23-2006 16:42:12

    An Error occured while exporting table CorrespondenceCompanyInfo

    Time : 01-23-2006 16:42:12

    An Error occured while exporting database WINLANCE

    Time : 01-23-2006 16:42:12

    An error occured while importing table. Please check the error file.

    Time : 01-23-2006 16:42:12

    pSql65Server->DumpAllTables () failed. hr=-2147467259

    Import Exit Code: -1 - ~cnvpipe1

    Msg 2601, Level 14, State 3, Server BRCTST, Procedure , Line 1

    [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot insert duplicate key row in object 'Ticket' with unique index 'TicketId_idx'.

    Msg 4849, Level 16, State 2, Server BRCTST, Procedure , Line 1

    [Microsoft][ODBC SQL Server Driver][SQL Server]Could not import table '[WINLANCE].[dbo].[Ticket]'. Error 3602.

    Structure was created, but if I subsequently try to pull the data via DTS from the original (different) server into this SQL 2000 instance, then I get a "cannot insert duplicate key row in object 'Ticket' with unique index....."

    SQL 6.5 had no issues with these tables. Is there an option I need to select during upgrade to get it working?

    Thanks,

    - JB

  • I think you will need to look at the data in the tables.

    A couple initial thoughts:

    You may have a duplicate key in the source table as a result of corruption or some other manipulation that may have been allowed in SQL 6.5

    You may have a different collation, causing a column that is unique in the source to be a duplicate in the destination.

    I'm sure there are plent of other possible problems, but these two I've actually dealt with before.

    hth jg

     

     

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply