comparison options between sql7 and sql2000

• 
  Hi there,
  
  Sorry about your problems. Just a few quick questions. Could you please double check that it is not something like a difference in the nullablity of the identity column that is causing the problem?
  
  Is it possible for your to post an example script of the SQL 7 and SQL 2005 tables? This might help us get the bottom of the problem quicker.
  
  Many thanks,
  
  Jonathan

  JonathanWatts May 25, 2006 05:00

  - 0 +
• 
  ok, here they are:
  sql7
  CREATE TABLE [dbo].[CROSS_BENEFIT]
  (
  [IDCROSSBENEFIT] [int] NOT NULL IDENTITY(1, 1),
  [IDBENEFIT] [int] NOT NULL,
  [IDCOUNTRY] [int] NOT NULL,
  [IDTYPEDIMENSIONGROUP] [int] NOT NULL,
  [DATASENSE] [int] NOT NULL,
  [NUMEROSITY] [int] NULL,
  [PERCENTAGE] [real] NULL
  )
  
  sql2005
  CREATE TABLE [dbo].[CROSS_BENEFIT]
  (
  [IDCROSSBENEFIT] [int] NOT NULL,
  [IDBENEFIT] [int] NOT NULL,
  [IDCOUNTRY] [int] NOT NULL,
  [IDTYPEDIMENSIONGROUP] [int] NOT NULL,
  [DATASENSE] [int] NOT NULL,
  [NUMEROSITY] [int] NULL,
  [PERCENTAGE] [real] NULL
  )
  
  
  These are the tables, SQL Compare highlights IDENTITY(1, 1)
  in the options I checked, beyond the default options,
  'Constraint and index names'
  'Identity seed and increment values'
  'Collations'
  'Indentity properties'
  
  thank you

  ziotempa76 May 25, 2006 05:19

  - 0 +
• 
  Hi there,
  
  I have run SQL Compare 5.1 over the tables above. However, I cannot get the tables to report as different.
  
  Whilst SQL Differences panel will still highlight the identity as a difference, it is not considered when determining the status for an object (Different, Identical, Only in db 1 or db 2).
  
  Is this the full syntax for the table or are there constraints, indexes, permissions etc on the table too? As these may be causing other differences that force SQL Compare to say this object is different.
  
  Hope this makes sense.
  
  Jonathan

  JonathanWatts May 25, 2006 08:48

  - 0 +

Add comment

Please sign in to leave a comment.