TempDB ran out of space on one of the production SQL Server 2005 DB with enabled Read Committed Snapshot.
By monitoring TempDB, it was known that Version Store was growing at a steady rate 1GB per day.
If the Version Store completely fills TempDB, the SQL Server is supposed to attempt to shrink the Version Store.
However, it doesn't in this case.
It's because some sessions connected by implicit transaction are taken as open transaction and Read Committed Snapshot cannot release the objects in that Version Store until transaction commit by IS restart.
Once the Version Store fills up, it will get into a stable state until IS restart, but may leave TempDB in a non-robust state.
To avoid this issue, it's considered to disable Read Committed Snapshot on SQL Server 2005 DB.
But is this supported with IS 7.1.2?
[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSVYEV","label":"IBM webMethods Integration"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"webMethods Integration Server (PIE)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Win Server 2003 Enterprise Edt"}],"Version":"7.1.2"},{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSFIWYE","label":"IBM webMethods B2B"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"webMethods Integration Server (PIE)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Win Server 2003 Enterprise Edt"}],"Version":"7.1.2"},{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSQG2X","label":"IBM webMethods Managed File Transfer"},"ARM Category":[{"code":"a8mKe00000000AQIAY","label":"webMethods Integration Server (PIE)"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Win Server 2003 Enterprise Edt"}],"Version":"7.1.2"}]
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.