Different stored procedures depending on database schema #1286
-
I have encountered this problem using version 1.2.0 of the DMS framework and the provider 'SqlSyncChangeTrackingProvider'. Provisioning a table located in the default schema of the database (in this case 'dbo') using a 'CustomWhere' to filter the synchronization by a particular field, it is observed that the following stored procedures are created, including those necessary to select the changes by the configured filter. On the other hand, if the table to be synchronized is in another schema of the database (such as the 'js' schema), when provisioning the table in the same way and with the same filter, the necessary stored procedures are not created to filter the changes by the configured parameter. Any idea why this is happening? I need to use the 'js' schema to provision all the procedures to be able to filter by the configured parameter. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Can you help me please? |
Beta Was this translation helpful? Give feedback.
that's incorrect:
Should be :
Or even