I have servers with lots of client databases, all with very similar, but not necessarily identical schemae.
Some customers want their data in MSAccess on a monthly basis. This was getting tedious to do on a manual basis, so I figured I would create SSIS packages for these exports, add them to a job, and be done with it.
I was hoping I could just create one DTSX file in the filesystem and change the database name, but I ran into schema differences between instances already so that won't work.
One issue that occurred to me is that when our developers change the source database schema, I'm guessing the SSIS packages won't know about the new tables.
Is there an easy way to deal with this?