Settings and activity
3 results found
- 
108 votesAn error occurred while saving the comment Andrew Hinson supported this idea · 
- 
20 votesAndrew Hinson supported this idea · 
- 
6 votesAndrew 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! 
 
        
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!