# \[RELEASE\] ScyllaDB Enterprise 2022.2.19

**URL:** <https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-19/1905>\
**Category:** Release Notes\
**Tags:** enterprise, enterprise-release, enterprise-2022-2\
**Created:** [April 30, 2024, 9:49am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-19/1905 "2024-04-30T09:49:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tzach](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tzach/32/172_2.png) [@tzach](https://forum.scylladb.com/u/tzach)\
**Post date:** [April 30, 2024, 9:49am UTC](https://forum.scylladb.com/t/release-scylladb-enterprise-2022-2-19/1905/1 "2024-04-30T09:49:13Z")

</div>

The ScyllaDB team announces ScyllaDB Enterprise 2022.2.19, a bug-fix production-ready ScyllaDB Enterprise patch release for [ScyllaDB Enterprise 2022.2 Feature Release.](https://forum.scylladb.com/t/scylladb-enterprise-release-2022-2-0/269)

Note the latest ScyllaDB Enterprise release is [2024.1 LTS](https://forum.scylladb.com/t/scylladb-enterprise-release-2024-1-0/1292), and you are encouraged to upgrade to it in coordination with the ScyllaDB Support team.

Related Links

- [Get ScyllaDB Enterprise 2022.2.19](https://www.scylladb.com/download/#enterprise) (customers only, or 30-day evaluation)

- [Upgrade from 2022.1.x to 2022.2.y](https://enterprise.docs.scylladb.com/enterprise/upgrade/upgrade-enterprise/upgrade-guide-from-2022.1-to-2022.2/index.html)

- [Upgrade from ScyllaDB Enterprise 2022.2.x to 2024.1.y](https://enterprise.docs.scylladb.com/branch-2024.1/upgrade/upgrade-enterprise/upgrade-guide-from-2022.2-to-2024.1/)

- [Upgrade from ScyllaDB Open Source 5.1 to ScyllaDB 2022.2](https://docs.scylladb.com/master/upgrade/upgrade-to-enterprise/upgrade-guide-from-5.1-to-2022.2/index.html)

- [Submit a ticket](https://supportscylladb.zendesk.com/hc/en-us/requests/new)

The following issues are fixed in this release (with an open-source reference, if available):

- MV Correctness: in some cases, like one base table with many views, updates to MV might be lost. In one example range tombstones made the issue appear earlier [#17117](https://github.com/scylladb/scylladb/issues/17117).

- Stability: wrong range used for partition estimation for mixed-shard repair, when different nodes have different shared counts, resulting in larger than needed filters [#17863](https://github.com/scylladb/scylladb/issues/17863).