Ok, so I feel for DBA's who do this regularly. It can be very overwhelming to say the least. Here is my question and scenario.
I'm attempting to work out an ETL process for 12 databases. All are the similar such as LIMS, LIMS-1, LIMS-2 etc. There are 12 of these. Seven have an identical schema, 4 have an identical schema but not identical to the first 7. Then 1 has a schema different that the other 11.
Migrating schemas probably isn't the challenge, however, I've never done this before so any tools to help would be great to know about. The problem comes in with stored procedures. There are over 100 applications that would use this new database (hence the problem). If there are stored procedures that have the same name, but operate on a different schema, what would be a way to handle this. I first thought about renaming the stored procs and then make changes to the application. However, my manager isn't wanting to go down that route. Thanks in advance.