Removing Custom Schema Extension in PRD

ObjectBrowser:

QBM_PColumnDrop @TableName nvarchar(64), @columnname nvarchar(64)
QBM_PTableDrop @TableName nvarchar(64) , @force bit = 0
and then compile the database.

Hello Niels,
Thank you for the answer but why do you refer to the ObjectBrowser ? 
Isn't it to be launched from SQL Server Management Studio instead ?
Many thanks.
Michel

Hello Niels,
Thank you for the answer but why do you refer to the ObjectBrowser ? 
Isn't it to be launched from SQL Server Management Studio instead ?
Many thanks.
Michel

Hello Michel,

The object browser should be fine if you use a SQL server connection with the dbname_Admin (AdminUser) account or the SQL install account (SysAdmin) or use SQL studio. Or temporary change the Staging level as suggested above in the post.
P.s. make SQL backup first do it in a change window and always try it out in a test environment first. 

Hello Niels,
Thank you for your answer but I am not at ease with changing the staging level because I have many dynamic roles that refers to DialogDatabase.ProductionLevel in their definition.
Beside that, the support told me using QBM_PTableDrop  is not safe. 
No solution to remove the useless tables then. Not very critical but it's a pity.
Regards,

Michel

I can understand the support standpoint not knowing the dependencies of the custom table in your environment.
You could disable the schedules used by these dynamic roles during the operation, but then again like you said it's not critical.

The support did not really alerted about the potential dependencies of the custom table, but simply presented instead the procedure QBM_PTableDrop as not safe in that context. In the end I don't know in which context that procedure can be used. But anyway that is a good idea to disable the schedule that compute dynamic roles. Simple but probably safe. Many thanks for this suggestion !