I agree. I have run into two cases where I wanted to use the tool but automatic mapping was not up to the job for tables, views or stored procedures. Any of these element names could change and it is annoying that I cannot map when it makes sense.
I have also begun using schema to differentiate parts of a monolithic legacy database which means for those elements, automatic mapping is not working.
A similar type of change involved consolidating two related databases again using schema to differentiate. Wanted to compare the original database to the related portion of the new. Not surprised that the automatic mapping failed in this case also but if I could map the views and stored procedures it could have been done.
Shawn Karr
supported this idea
·
I agree. I have run into two cases where I wanted to use the tool but automatic mapping was not up to the job for tables, views or stored procedures. Any of these element names could change and it is annoying that I cannot map when it makes sense.
I have also begun using schema to differentiate parts of a monolithic legacy database which means for those elements, automatic mapping is not working.
A similar type of change involved consolidating two related databases again using schema to differentiate. Wanted to compare the original database to the related portion of the new. Not surprised that the automatic mapping failed in this case also but if I could map the views and stored procedures it could have been done.