Hi,
I'm recreating test set of tables from an existing database into DDT. We use GUIDs throughout as the PK for each table and I notice the tables created by the DDT all have their RowGuid property set to No whereas the current tables are all set to Yes. The defualt value for the PKs are are to (newid()).

In all original tables we set RowGuid to Yes because that, is indeed, what the column is however I not sure what would have happened had we said No.

My question is: should I change all the settings in DDT so that all out GUID PK's have a RowGuid value of Yes?

TIA - Peter

Hi Ben,

Thanks for that. Actually this is interesting because the reason we use GUIDs is that the app does support replication. So, in this case, should we be changing the RowGUID value to Yes?

Cheers, Peter

Replication requires that all tables being replicated have a RowGuid somewhere on the table, so yeah, I would go ahead and turn it on on your PK columns... there's no reason to have another 16 bytes per record taken up by another GUID when you already have one