Table name being cut off when migrating DB changes to different environment
When my team try to migrate any DB changes from our development environment to our test environment the table names are cut off.
Ex: In a Product rule we include a Database table rule that is mapped to the table XX-Counterparty.
When we import this product in the test environment, Pega tells us that there are schema changes and the SQL that Pega suggest is "Create Table" instead of "Alter Table". It wants to create a table named XX-C01cbd instead of alter the table XX-Counterparty.
The XX-Counterparty table exists in both environment so everything should work.
Also, if we continue with the import, Pega doesn't do anything to the database. The table that is suggested (XX-C01cbd) is not even created. Pega seems to just ignore the entire thing.
It appears that the names of the tables are being cut of at a specific length, which got us thinking that maybe we just have to make sure all our tables have shorter names and everything should be fine.
However, we asked a colleague that works in the same server environments but on a different application to try and import the Product for us and for him everything worked as expected. The table is recognized and Pega automatically alters the table in a correct manner.
I'm not sure how to troubleshoot this. Are there any access right within Pega that could be causing this for us but not for others in the environments?