[sims] SIMS why can’t I apply a patch as part of a Schedule update sequence

[nicholab]

Why Capita can't I apply a patch as part of a Schedule I want to apply Patch 24825 after I moved to the latest version of SIMS. But Captia you stopped me being a grown up and Scheduling all the updates and then the patch why did you let the developers make such a naff option?

 

Also why cant I just get all the update for all products and then apply in the Capita approved sequence?

 

I want a button that says update and to be able to set a time that is all!!!

Edited April 8, 2019 by nicholab

[ajp233]

If you use SOLUS you can deploy patches on a scheduled basis

[nicholab]

You can but it will not let you deploy an update that needs a certain DB version unless you have the update that is scheduled to be deployed?

 

You cant't do Full version>Patch if certain DB version is needed.

[Banjo]

You can, you just need to do it outside of Solus. You can do DB upgrades and patching from the cmd line and schedule these using Windows Sched. Tasks.

[matt40k]

You can, you just need to do it outside of Solus. You can do DB upgrades and patching from the cmd line and schedule these using Windows Sched. Tasks.

That's called effort. The goal is hands free.

[nicholab]

You can, you just need to do it outside of Solus. You can do DB upgrades and patching from the cmd line and schedule these using Windows Sched. Tasks.

 

Pleases show me how that can be done as I normally what to do all SIMS update in one go?

 

Thanks

[Esteban_Child_of_the_Sun]

You can do it through the SOLUS3 UI. When scheduling the upgrade, hold down CTRL and also select the patch at the same time as the upgrades, this allows you to schedule both at once as it only does the DB version check against the release selected and not the patch.

[Damon]

You can do it through the SOLUS3 UI. When scheduling the upgrade, hold down CTRL and also select the patch at the same time as the upgrades, this allows you to schedule both at once as it only does the DB version check against the release selected and not the patch.

[ATTACH=CONFIG]53047[/ATTACH]

[ATTACH=CONFIG]53048[/ATTACH]

[ATTACH=CONFIG]53049[/ATTACH]

 

Does it assign the deployment order automatically though? Just wondering if it may run them based on release date.

 

We often run patches via Centrastage which makes things a bit easier. From memory, run dbattach from the cmd line with a /? switch. As Matt said though, the OP's original point stands, regardless of this workaround.

[Esteban_Child_of_the_Sun]

I haven't needed to do it in a while so haven't tested it yet as we are yet to deploy the release. You can always alter the time of the upgrade once scheduled to make sure it happens before the patch.