Skip to content

Settings and activity

3 results found

  1. 102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  SQL Compare  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Andrew Hinson commented  · 

    I have this issue. We store a Location Identifier as a column default constraint and do so in over 100 databases. The lack of a way to ignore default constraints makes SQL Compare difficult to use, since every table appears under "in both, but different" as a false positive. Make this happen, please!

    Andrew Hinson supported this idea  · 
  2. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Compare  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Andrew Hinson supported this idea  · 
  3. 6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Compare  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Andrew Hinson supported this idea  · 
    An error occurred while saving the comment
    Andrew Hinson commented  · 

    I have this issue. We store a Location Identifier as a column default constraint and do so in over 100 databases. The lack of a way to ignore default constraints makes SQL Compare difficult to use, since every table appears under "in both, but different" as a false positive. Make this happen, please!