What are the challenges you face when working across database platforms? Take the survey
Options

Blank lines detected with compare, but not applied

mzcopeamzcopea Posts: 31
edited May 16, 2006 9:20AM in SQL Compare Previous Versions
We are using Sqlcompare commandline to create our scripts. We are noticing that Sql Compare produces a huge script when we don't expect to have many or any changes. What we have noticed is that Sqlcompare detects a change in functions, views or stored procedures that may just be an extra blank line.
Though it detects the blank line as a change, it doesn't make the change on the destination database objects. Therefore, week after week, we have the same script changes that only appear to be extra blank lines that never get applied.

Any ideas would be appreciated.

Comments

  • Options
    TilmanTilman Posts: 395 Bronze 2
    Hi,

    have you tried the IgnoreWhiteSpace option? It should be part of the default options. To specify it explicitely add:

    /options:IgnoreWhiteSpace

    to your command.

    For more information on options see the verbose help of the command line, i.e.

    sqlcompare /help /verbose.

    Let me know if that helps.

    Tilman
  • Options
    YES! Wonderful! My compare script went from 1.7 meg to 12KB. This will eliminate some of our build problems because the script would run into constraint issues unneccesarily due to attempting to make changes that were unneeded.

    It's the little things that mean so much.

    Thanks!
This discussion has been closed.