Comments
Sort by recent activity
Ah ha! Just worked it out. The synchronisation included 113 objects being added or updated "from left to right", but also 2 objects to be deleted from the right side. When the two objects to delete are removed, it all works fine. / comments
Ah ha! Just worked it out. The synchronisation included 113 objects being added or updated "from left to right", but also 2 objects to be deleted from the right side. When the two objects to delete...
I have just come across this problem too. The only difference I can discern from my ususllay successful comparisons, is that this comparison includes more objects than usual (115).
In answer to your questions;
1) I am comparing 2 live databases
2) It doesn't matter which synchronisation method I choose: the same problem occurs with both
3) V7 won't work because I am comparing SQL Server 2008 (Standard - fully patched).
Thanks in advance
Lewis / comments
I have just come across this problem too. The only difference I can discern from my ususllay successful comparisons, is that this comparison includes more objects than usual (115).
In answer to you...
Hi Tilman
Thanks for the response. I don't think I have changed any of the defaults - but I might have!
It must be due to the specific syntax I have in the rest of the stored procedure. It's over 400 lines long, so I won't post it here. I have tried to extract a snippet which will reproduce the behaviour but I am unable. In fact, it is now doing something different (but also naughty) i.e.
IF NOT EXISTS (SELECT ...)
BEGIN
{type DELETE in here}
INSERT INTO ...
END
After typing DELETE and pressing SPACE, the above becomes:
IF NOT EXISTS (SELECT ...)
BEGIN
END
INSERT INTO...
END
i.e. the DELETE disappears to be replaced with END.
I could send you the whole stored proc if you like?
Cheers
Lewis / comments
Hi Tilman
Thanks for the response. I don't think I have changed any of the defaults - but I might have!
It must be due to the specific syntax I have in the rest of the stored procedure. It's over 4...