Activity overview
Latest activity by PeterH
@Paul_H I've found a very simple work-around. The script generated puts all the inserts at the end, so update statements fail because they're happening before the rows to which they sometimes refer are created. So I take the option to export the deployment script to SSMS, then cut and past all the inserts (handily all blocked together) to the top of the script, so all new rows are created first, and thus available as FK references to later updates. Given it all runs in a transaction, I'm unclear why this isn't the default behaviour, but that's way above my pay grade. This means sync scripts run 100% reliably every time. Hope this may help you. / comments
@Paul_HI've found a very simple work-around. The script generated puts all the inserts at the end, so update statements fail because they're happening before the rows to which they sometimes refer ...
Is there any update on this capability? I just bought SQL Data Compare, and want to push production data to a staging database. I would like the tool to work a bit harder and figure out which tables are at the bottom of the dependency tree and update those first, then work its way back up so that the "lookup tables" get their updates first, and thus FK references are always kept in place during the update process. Is this on the list of things to do, or maybe it's already been done? (*crosses fingers*) / comments
Is there any update on this capability? I just bought SQL Data Compare, and want to push production data to a staging database.I would like the tool to work a bit harder and figure out which tables...