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

refresh after synchronization

OlegOleg Posts: 83
edited December 20, 2005 2:07PM in SQL Compare Previous Versions
I do synchronization, refresh and the same objects are different again.
Difference is in whitespaces. But as for me after sync objects must be equal.

Comments

  • Options
    Hi Oleg,

    This sounds like an issue we are investigating. Is the white space problem one new line at the end of an object on a SQL2005 database?

    Regards,

    Jonathan
    Jonathan Watts

    -Project Manager
    -Red Gate Software Ltd
  • Options
    Hi Jonathan,
    its the first object (end of proc)
    1(2005)
    if @trancount>0
    begin
    if @status=0
    commit tran
    else
    rollback tran
    end


    end



    GO
    2 (2000)
    if @trancount>0
    begin
    if @status=0
    commit tran
    else
    rollback tran
    end

    yok, kyrdyk

    end



    GO
    end of 2




    The difference is here
    end

    <

    GO


    Regards,
    Oleg.
  • Options
    Oleg wrote:
    I do synchronization, refresh and the same objects are different again.
    Difference is in whitespaces. But as for me after sync objects must be equal.

    Hi Oleg,
    as Jon mentioned there is an issue with tailing newlines when migrating from 2000 to 2005. This is because of the way 2005 "eats" some newlines. At the moment the only way around it is to set "ignore whitespace" to on, but we are looking into this bug. Note that 2000 to 2000 migration, as well as 2005 to 2005 migration should work.

    Regards,
    Andras
    András Belokosztolszki, PhD
    Red Gate Software Ltd.
This discussion has been closed.