Mapping to an existing source doesn't work like expected

[Peter13]

We use SQL Data Generator to anonymize production data: we copy a table, we tell Data Generator to populate the copy, we assign the original table as the data source ("Use existing data source") and then we assign generators to columns that contain sensitive data.

This works fine in version 1, but since we switched to version 2 (and SQL Server 2012) Data Generator no longer automatically maps the original columns to the copy table. This means we have to map the corresponding columns manually. Is there a way to tell Data Generator 2 to behave like it used to in version 1? The documentation for version 2 tells me it should still work as before, but somehow it doesn't.

[Brian Donahue]

We are dealing with your request via the support ticket that you logged via email. I'll update this forum topic if we can work out what the problem is.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521

[Peter13]

Because other visitors of this forum can't read my support ticket, I will inform them this way about our proceedings:

Red Gate has determined that the automatic column mapping functionality has disappeared between version 1 and 2 an has no idea when it will be fixed. Leaving me, of course, very disappointed. Why do you remove functionality when upgrading a product without notifying your users? The only reason I can think of is you want to sell your product "SQL Data Refresh". Which, by the way, doesn't satisfy our needs because SQL Server 2012 isn't supported.

[Peter13]

Still no indication from Red Gate when this will be fixed.

Apparently this issue is no problem for other Data Generator users, since I don't read any other complaints... Are we the only ones who use Data Generator to generate test data based on production data?