Of course SQL Compare warns of thoretical truncation when you alter data types or field lengths, but it doesn't check whether any data actually exists in the source database that will be truncated, let alone help you find those records. So:
A pre-synch report of data that would be truncated would be a super enhancement.
If you don't care about the truncation (or hope it doesn't matter!) and need the synch to work 'by brute force', why isn't 'ANSI Warnings OFF' or 'Allow data truncation' a project option. I'm not aware of any way of doing this except editing the script.
Steve
A pre-synch report of data that would be truncated would be a super enhancement.
If you don't care about the truncation (or hope it doesn't matter!) and need the synch to work 'by brute force', why isn't 'ANSI Warnings OFF' or 'Allow data truncation' a project option. I'm not aware of any way of doing this except editing the script.
Steve