Thanks fro your question. There are many possible meanings that this question could have, but I'd think both issues could be served by using the "data masking" instructions in the help.
That way, you can use some existing data in the generated data because you have created a copy of the schema and have configured SQL query generators to pull the original data across.
I Followed your instructions and it looks like the primary key is still "server assigned". I tried it and it did replace my PK with a new reseeded one starting at 1 which will not link correctly to all my other tables related to it.
We do not want to change the PK. on multiple tables in the DB. Am I missing something in the directions?
Sorry for the misunderstanding. I will log an enhancement request to allow you to change the server-assigned primary key. It doesn't look to be possible to do this.
SQL Data Generator cannot leave a column in a table because it is designed to generate realistic test data, and not as a data sanitization application. Red Gate recognize a small market for this, and that is why the help article exists to help you accomplish that in a roundabout way.
SQL Data Generator has a hard-coded "server assigned" generator for IDENTITY columns that you cannot change because identity columns have to conform to the constraint on the server anyway (seed value, increment, and current value). The topic was primarily about that, so I was going to raise a feature request to allow "at your own risk" changes there if there is a need for it.
wwilkins
Posts: 5
Comments
http://documentation.red-gate.com/displ ... ata+source
That way, you can use some existing data in the generated data because you have created a copy of the schema and have configured SQL query generators to pull the original data across.
We do not want to change the PK. on multiple tables in the DB. Am I missing something in the directions?
SQL Data Generator has a hard-coded "server assigned" generator for IDENTITY columns that you cannot change because identity columns have to conform to the constraint on the server anyway (seed value, increment, and current value). The topic was primarily about that, so I was going to raise a feature request to allow "at your own risk" changes there if there is a need for it.