After triggering the schema deployment in designer, the new schema is transfered to server and the server proceedes with its activation (rollout of new schema, necessary database changes, update of rolesystem). However, in order to conclude the activation process, it is necessary that all tasks, that were running at the moment of activation, are finished in order to ensure consistent state of a system after activation.
This may cause a delay in activation if there are long-running tasks in the system. Since system is not fully available until activation process is completed, when activating schema in a production systems, the administrators are advised to ensure that there are no long-running tasks at the moment of activation. management studio provides the list of currently running taks as well as the list of scheduled tasks. The focus in on tasks with considerable duration to complete, such as archiving of large number of objects or reindexing. The tasks with short duration, such as subscription tasks do not have to be interrupted or paused in the scheduler, since the delay that they introduce is negligible.
This explanation applies to all released redline versions.