Post reply

Poor Man's Table Difference

  • May 4, 2010 at 2:28 pm

    #218539

    Comments posted to this topic are about the item Poor Man's Table Difference

  • May 6, 2010 at 7:54 am

    #1163219

    Thanks for posting. It's a difficult problem at times; I was hoping I could borrow your approach for my own situation. But doing the True General Proc for this kind of thing would have to be a major project in its own, I can tell you.

    My own situation is copying from ASE to SS; there are so many issues to be found - even things like "user copied a string with smart quotes from MS Word into a varchar field"; which is a character set incompatability no matter how well you try to match them.

    My own choice to generate line-based text files and use Unix's sort/diff to get the cross platform differences had its problems too.

    On pure SQL Server, however, I'm usually just using "except" with a little logic. Running on 64-bit servers, it's amazing how much can be done how quickly to find differences between results (not just "base tables", any result).

    You gotta do what works. Too bad Fabian Pascal's predicted world of DRDBMS never came to pass.

    Roger L Reid

  • May 6, 2010 at 11:24 am

    #1163465

    If you're going to sync the DB's then eventually you need to find out what column/row is different. This solution doesn't address specific column and row to update in order to sync them which opens up a big can or worms.

  • May 6, 2010 at 7:26 pm

    #1163734

    jddddd2,

    Just happens for my case that if the row is different, the newest row is plastered onto the other copy. But you're right...if the requirements need to look at columns, something more would be needed.

  • May 19, 2016 at 6:58 am

    #1880198

    Thanks for the script.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply