Activity overview
Latest activity by sparco
Thank you for the reply.
I see the reasoning behind the change and the workaround helps but still requires a little bit of effot. It seems that you have the functionality in place within the script engine to do a full rebuild so can you not just add a tick box control the mechanism for all tables. The logic would be:
--Determine If Column Order Changed
ColumnOrderChanged = ColumnOrderChanged OR ForceFullTableRebuild
Selecting per table would be cool but would require more effort etc. The above looks relatively simple to implement.
Cheers
Craig / comments
Thank you for the reply.
I see the reasoning behind the change and the workaround helps but still requires a little bit of effot. It seems that you have the functionality in place within the script...
Earlier version use to work differently:
- Create a temporary table based on the orginal schema
- Pump data into temporary table
- Drop the orginal table
- Recreate the table with the new column(s)
- Re-populate the newly created table
This gave you a chance to sort out what values should go into the new column. This was an excellent solution.
We purchased the new version which switched to the horrid add column implementation. We stopped using it because it was too time consuming re-coding all the add columns to use the old solution. We were more than happy to wait a few orders of magnitudes more for it do the comparison because we got the final script generated a lot quicker!
It would be great if you could introduce an option that allows you to choose how to deal with adding columns.
Cheers
Craig / comments
Earlier version use to work differently:
- Create a temporary table based on the orginal schema
- Pump data into temporary table
- Drop the orginal table
- Recreate the table with the new column(s)...