Hi ​@sashikant,

It depends.

If the database changes about be deployed via the delivery/patch are non-blocking and backward-compatible(new table, new view, new package, new index etc), you can proceed without downtime.

However, if they alter existing structures (existing tables, packages, methods, views, indexes etc), involve large data migrations, or risk performance issues(simply going to have any sort of possible impact on the existing transactions happening), setting maintenance mode is recommended.

https://docs.ifs.com/techdocs/23r2/070_remote_deploy/060_tips_managing_middle_tier/010_mtctl/

The impact of this delivery can be assessed using impact assessment/impact analysis using cloud build place.

https://docs.ifs.com/techdocs/ale/020_lifecycle/080_release_update_studio/040_after_applying_release_update_to_baseline/010_release_update_with_customization/010_impact_analysis/#trigger_impact_analysis_using_update_analyzer

Always make sure to test in staging before applying in the PROD and monitor performance post-deployment  as well.

Regards,

Binuri