The Jade 2025 release focuses on modernising the developer experience and helping you build faster, smarter, and more scalable applications.
[Please note, this is for JadeCare managed Deployments, so manually changing the alter scripts isn't an option.]
When Jade does a TABLE drop, it renames the table via the RPS alter script, it also re-applies the PRIMARY KEY index for that renamed table, for very large tables this can take hours.
In some case there is NO need to save off the table. But in most cases, there NO need to re-add the Primary key at the time the alter script is run. (this could be completed at a later stage if required, manually)
SQL-EXExxx sp_renamexxx 'STAGING_ACCOUNT_HISTORY', 'Jade_Dropped_14May2019@093034_STAGING_ACCOUNT_HISTORY'
SQL-ALTERxxx TABLE [Jade_Dropped_14May2019@093034_STAGING_ACCOUNT_HISTORY] DROP CONSTRAINT [PK_STAGING_ACCOUNT_HISTORY]
SQL-ALTERxxx TABLE [Jade_Dropped_14May2019@093034_STAGING_ACCOUNT_HISTORY] ADD CONSTRAINT [PK_Jade_Dropped_14May2019@093034_STAGING_ACCOUNT_HISTORY] PRIMARY KEY NONCLUSTERED ([oid])