Understandably, the code was originally intended for generating stored procedure code (which are your stored procs that would merge your tables) for 'all common' tables within a given pair of databases (source and destination). Specifying certain tables would require additional input parameters. The biggest reason why I don't use ssis for this, is because metadata within the ssis package can habitually fall out of sync and then you get errors. I try to keep as much of my database automation within the sql world as possible and as little against metadata driven ssis packages (which I've found to be tempermental on a windows 2003 server 64 bit environment with 2008 r2 sql server). I haven't gained enough confidence in ssis yet to use it as a replacement for something I could do writing dynamic sql to do. I guess it's a matter of personal taste.