Comments
Sort by recent activity
We've just released Figleaf 7.0.32! We've expanded the mask conditions feature in a couple of ways - you can now switch between different mask types based on the conditions (rather than just skipping rows) and we've added a new condition type where you can specify a list of values to match. You can download the latest version at http://download.red-gate.com/Figleaf.exe / comments
We've just released Figleaf 7.0.32! We've expanded the mask conditions feature in a couple of ways - you can now switch between different mask types based on the conditions (rather than just skippi...
We've just released Figleaf 7.0.20.3670! For the past few weeks we've been looking into defining custom relationships to preserve in the database (for the cases where foreign keys don't exist) but in the meantime we've been pushing out a few releases with various bugfixes. In particular this release fixes a few quality-of-life issues with the column selection scrolling behavior / comments
We've just released Figleaf 7.0.20.3670! For the past few weeks we've been looking into defining custom relationships to preserve in the database (for the cases where foreign keys don't exist) but ...
We've just released Figleaf 7.0.17.3290! This release enables the feature flag for "build your own" template masks by default, which allows creating data with a custom pattern in a straightforward manner. It can be downloaded via https://www.red-gate.com/projectfigleaf or through the autoupdate inside the product. / comments
We've just released Figleaf 7.0.17.3290! This release enables the feature flag for "build your own" template masks by default, which allows creating data with a custom pattern in a straightforward ...
Sorry about this! We're investigating it now. It looks like an update to one of our shared libraries might have had some unexpected effects. We'll let you know when we have a fix available. / comments
Sorry about this! We're investigating it now. It looks like an update to one of our shared libraries might have had some unexpected effects. We'll let you know when we have a fix available.
Sorry for the delay here - I think we've tracked down the problem, so hoping to have a fix released some time this week if possible. / comments
Sorry for the delay here - I think we've tracked down the problem, so hoping to have a fix released some time this week if possible.
Honestly I'm not exactly sure what's causing your problem at the moment (it's been some time since we implemented temporal table support so the code isn't particularly fresh in my head) but I think the cause is to do with the way that SQL Compare currently just reads the name of the history table and deploys that, rather than treating the history table as an independent object with its own properties.
I think you're probably right in that this case it's more likely to be a problem with mappings than a problem with customisation as such, but if we have the history table as its own thing in the code then we're more likely to be able to apply mapping to it properly.
Either way, I'll try and make sure we do something to improve this situation [image] / comments
Honestly I'm not exactly sure what's causing your problem at the moment (it's been some time since we implemented temporal table support so the code isn't particularly fresh in my head) but I think...
Thanks for the feedback - this is actually something we're hoping to look at soon. Our current implementation of temporal table support in SQL Compare doesn't preserve any customisation on the history table, such as putting it into a different schema (like the case here) or adding extra indexes and constraints (which some of our other customers have run into). We'll be looking to see if we can improve the situation so that we do a better job here, although we want to try and avoid complicated dependency issues that could arise if we start treating the history table as another first-class table. / comments
Thanks for the feedback - this is actually something we're hoping to look at soon. Our current implementation of temporal table support in SQL Compare doesn't preserve any customisation on the hist...
This isn't currently a feature in SQL Data Compare as far as I know, but you could write a script based on sp_MSForEachTable such as the one described here: https://stackoverflow.com/a/156813/895407 before doing the SQL Data Compare comparison. Would that work for you? / comments
This isn't currently a feature in SQL Data Compare as far as I know, but you could write a script based on sp_MSForEachTable such as the one described here: https://stackoverflow.com/a/156813/89540...
Hi - I'll take a look at the discussion in https://forum.red-gate.com/discussion/81291/truncate-target-database-first-then-insert-the-source-data since this appears to be a duplicate / comments
Hi - I'll take a look at the discussion in https://forum.red-gate.com/discussion/81291/truncate-target-database-first-then-insert-the-source-data since this appears to be a duplicate
We don't have this in Compare itself at the moment, but if you want to work with migration scripts you can do so through SQL Source Control - eg there's a worked example here: https://documentation.red-gate.com/display/SOC5/Splitting+a+column+without+data+loss / comments
We don't have this in Compare itself at the moment, but if you want to work with migration scripts you can do so through SQL Source Control - eg there's a worked example here: https://documentation...