T
temays
Guest
Valeriy, The SQL generation is working as designed. Keep in mind that typically SQL generation is done prior to any table mapping , hence the generator always reads the entire contents of the source database, and in your case created the DDL to fully build the source schema on the target. When you run fully synchronized schemas, Pro2 can you assist in keeping them synchronized, even when applying changes to the source db (SQL Diff Tool). However, for sure you are not required to run synchronized schemas, so doing a drop on the 600 tables is certainly at the discretion of the customer. Be aware the SQL Diff will no longer be of value as it will always want to add back the schema for the missing 600 tables. You do bring up an interesting idea. In your case the full schema generation was loaded, you then mapped tables and wanted to regenerate the SQL. Should Pro2 only generate DDL for tables in which mapping exists? I'll take that as an enhancement request and explore how it might work. It could get tricky within the SQL diff in regards to detection of new tables to source, versus tables that are being ignored. So for sure it requires some thought. Thank your for your question and hope this helps. Terry Progress Engineering Group
Continue reading...
Continue reading...