Schema not recognised

• 
  Hi Ronald,
  
  What status are the databases currently shown as? Are they red, i.e. drifted, or are they green, i.e. acknowledged?

  Rob C November 23, 2015 05:53

  - 0 +
• 
  They are currently in drifted because i made the same change on both databases (so they are still the same), i did that so i could get the debug files (h x2)

  ronaldvanhelden November 23, 2015 06:24

  - 0 +
• 
  If you acknowledge the schema for one database and enter a schema name, does the other database go orange and display the schema name to reflect that the schema is known?

  Rob C November 23, 2015 06:41

  - 0 +
• 
  No, the first database will change to the named scheme, the other database remains in drifted state

  ronaldvanhelden November 23, 2015 06:50

  - 0 +
• 
  Could there be differences in column order? DLM Dashboard will treat these as differences, but SQL Compare ignores them by default. Try doing a comparion using SQL Compare but with the Force column order option enabled. Does that detect any differences?

  Rob C November 23, 2015 06:55

  - 0 +
• 
  I have tried with sql compare with the force column order option, but the databases are still equal

  ronaldvanhelden November 23, 2015 06:58

  - 0 +
• 
  Hi Ronald,
  
  I have created a support ticket for you and you should receive an email shortly.

  Rob C November 24, 2015 09:48

  - 0 +
• 
  Was this ever resolved, I'm having the same issue. SQL Compare has no differences but says that one of my databases has drifted.

  carthorn May 25, 2016 11:21

  - 0 +
• 
  I am experiencing this problem still as well.

  josh_stcu October 10, 2017 22:26

  - 0 +
• 
  I'm sorry to say it's a known issue where DLM Dashboard incorrectly detects differences because sub-objects in the two databases are being scripted in different orders. However, we have not been able to prioritize it for bug fixing.

  Tianjiao_Li October 19, 2017 12:53

  - 0 +

Add comment

Please sign in to leave a comment.