Hi @rvgfox can you please add a few screenshots of your setup and the steps taken to reproduce the error? Thanks!

I’ve two tables with the same name in diferent schemas:

The partition configuration it’s the same in both tables:

Now, I’m not be able to reproduce the error, but in the SQL Server both tables share the same partition schemas and partition functions and if one deploy & execute proccess try to drop and recreate one of the tables it gets an error.

Are your databases for DSA and MDW separate or the same one? If the latter, do you have a default schema behaviour for all items in DSA and MDW? If not, I guess it may be that TX overwrites the DSA objects with MDW ones if you deploy the latter.

The database it’s the same, but they have diferent schemas:

Hi,

OK - could it be that some central objects for partitioning end up in the aux schema and then have the same name? I usually put the layer name in all schemas, especially when I am sharing a database. So dsa_etl, dsa, mdw_etl, mdw, etc.

Hi @rory.smith the problem isn’t in the schema name, it’s in the object name, it cannot be the same because in SQL server the partition schema and the function are created using the object name, without the schema.

Hi @rvgfox 

I was able to reproduce the issue.

The currency tables above have the same template and partition settings, and both deployed and executed successfully. However, once I deleted the “currencytype” field in the Sales data area (i.e. a field from the source table), I received the following error upon deployment of the Sales data area.

In order to resolve the error, I went back into table settings and set the table partition template to “None” on both tables. Then I was able to deploy successfully again.

I then changed the table partitioning back to the previous settings and it worked again. So as a workaround, can you please try setting the template to “None” on both tables, and deploy, before enabling the table partition template again?

@Christian Hauggaard  The workaround works for me, but I think that this error must be fixed.