# How to smoothly upgrade temporal server from v1.12.1 to higher version?

**URL:** <https://community.temporal.io/t/how-to-smoothly-upgrade-temporal-server-from-v1-12-1-to-higher-version/9861>\
**Category:** Server Deployment\
**Created:** [October 18, 2023, 3:11am UTC](https://community.temporal.io/t/how-to-smoothly-upgrade-temporal-server-from-v1-12-1-to-higher-version/9861 "2023-10-18T03:11:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![echolihao](https://avatars.discourse-cdn.com/v4/letter/e/5f9b8f/32.png) [@echolihao](https://community.temporal.io/u/echolihao)\
**Post date:** [October 18, 2023, 3:11am UTC](https://community.temporal.io/t/how-to-smoothly-upgrade-temporal-server-from-v1-12-1-to-higher-version/9861/1 "2023-10-18T03:11:25Z")

</div>

We are now using temporal server v1.12.1, and unfortunately we are using advanced visibility with MySQL as storage ☹ So we have the issue where the new `BuildIds` search attribute are not understood and cause errors in visibility processing.

The release notes show that v1.21.2 has fixed the issue:  
2023-07-12 - [71ae36c](https://github.com/temporalio/temporal/commit/71ae36c7517a906b972bfa27c1aa2fc5d887a51d) - Fix MySQL 8 upgrade script to schema v1.3 ([#4598](https://github.com/temporalio/temporal/pull/4598))

We plan to upgrade to higher version to fix the issue, now the problem is: We already have some workflow running in production env, we can just directly upgrade to a higher version(such as v1.21.2), or we need to fix the MySQL schema manually before we upgrade to a higher version? What should we do?

Thanks