Blank lines detected with compare, but not applied
mzcopea
Posts: 31
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.
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.
This discussion has been closed.
Comments
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
It's the little things that mean so much.
Thanks!