When migrating our SF, we noticed our SF has several stored procedures that are invalid. For example the stored procedure ins_usr_branch, which has an insert statement with columns that don’t exist in table usr_branch ("read_only","read_only_allow_merging"). So I looked at the 2025.3 install script 115_Handlers.sql and I noticed that ins_usr_branch is not included, so it seems ins_usr_branch should not exist.
I found that the upgrade from 2024.3 to 2025.1 (TSF_2025.1\SF\Upgrade\2024.3.11\115_Handlers.sql) created this stored procedure and in all upgrade scripts that came after this, it was never dropped.
We started with the SF 2024.1 installation and we always used the Deployment center GUI to upgrade our SF (up to 2025.3). So why are these stored procedures never dropped? And could there be more ‘old’ objects in our SF database schema that should not be there?
To fix this, is it safe to just execute the install code files 030-150 from the 2025.3 install package?
