What database isolation level does Liferay need for Microsoft SQL Servers?
Written By
Nathan Roberts
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
Environment
- Liferay Portal 6.2 connected to a SQL Server 2005, 2008, 2008 R2, 2012, or 2014 database
- Liferay DXP 7.0 connected to a SQL Server 2008, 2008 R2, 2012, 2014, or 2016 database
- Liferay DXP 7.1 connected to a SQL Server 2016 database
- Liferay DXP 7.2 connected to a SQL Server 2017 database
- Liferay Commerce connected to a SQL Server database supported for the DXP bundle hosting Commerce
Resolution
-
For SQL Server to function properly with the product (Portal 6.2, DXP 7.0, 7.1, 7.2, or Commerce), SQL Server’s Read Committed Snapshot Isolation level must be turned on. While other databases enable this behavior out of the box, it is disabled by default for SQL Server.
Did this article resolve your issue ?