# Revisited: MS SQL Server, RCSI and Continua database

**URL:** <https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334>\
**Category:** Bugs\
**Created:** [February 27, 2023, 10:45pm UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334 "2023-02-27T22:45:46Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bruce\_at\_ds](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@bruce\_at\_ds](https://www.finalbuilder.com/forums/u/bruce_at_ds)\
**Post date:** [February 27, 2023, 10:45pm UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/1 "2023-02-27T22:45:46Z")

</div>

Hi,

This is a revisit of a previous issue we had. See this post for reference:

[https://www.finalbuilder.com/forums/t/ms-sql-server-rcsi-and-continua-database/7162](https://www.finalbuilder.com/forums/t/ms-sql-server-rcsi-and-continua-database/7162)

Having installed Continua v1.9.2.1067 only a few days ago, our DB Administrator is reporting the same issue we had before.

> Same story as before: they have an open (and sleeping) transaction where they keep doing some update/insert and never close it. Tempdb will fill and prod will die eventually.
> 
> **You can send them this code:**
> 
> (@p0 nvarchar(128),@p1 nvarchar(128))select serverprop0\_.Id as id1\_18\_, serverprop0\_.Namespace as namespace2\_18\_, serverprop0\_.Name as name3\_18\_, serverprop0\_.Value as value4\_18\_, serverprop0\_.CollectedValue as collectedvalue5\_18\_, serverprop0\_.ElementType as elementtype6\_18\_, serverprop0\_.IsUserSupplied as isusersupplied7\_18\_, serverprop0\_.ReadOnly as readonly8\_18\_, serverprop0\_.Description as description9\_18\_, serverprop0\_.CollectorId as collectorid10\_18\_ from core\_serverproperty serverprop0\_ where [serverprop0\_.Namespace=@p0](mailto:serverprop0_.Namespace=@p0) and [serverprop0\_.Name=@p1](mailto:serverprop0_.Name=@p1) ORDER BY CURRENT\_TIMESTAMP OFFSET 0 ROWS FETCH FIRST 1 ROWS ONLY

He also comments:

> …also as before, RCS is turned off for their DB until fixed by them. Unless we get blocking with builds, maybe we just keep it off.

Can you please look into this?

Thanks,  
Bruce Palmer

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [February 28, 2023, 12:13am UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/2 "2023-02-28T00:13:53Z")

</div>

Hi Bruce,

Unfortunately, we are not seeing any stuck transactions on our test SQL Server installation of Continua CI, so to help us diagnose the cause of this issue, can you let us know which version you upgraded from?

---

<div class="post-metadata">

**Author:** ![bruce\_at\_ds](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@bruce\_at\_ds](https://www.finalbuilder.com/forums/u/bruce_at_ds)\
**Post date:** [February 28, 2023, 12:58am UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/3 "2023-02-28T00:58:36Z")

</div>

Hi Dave,

Previous version was 1.9.2.1066. Before that was 1.9.2.1056.

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [February 28, 2023, 2:00am UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/4 "2023-02-28T02:00:34Z")

</div>

Hi Bruce,

We can’t see any changes since v1.9.2.1056 which could have caused this issue. Is there any further information in the database logs on which update/insert transaction was not being committed?

---

<div class="post-metadata">

**Author:** ![bruce\_at\_ds](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@bruce\_at\_ds](https://www.finalbuilder.com/forums/u/bruce_at_ds)\
**Post date:** [February 28, 2023, 3:20am UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/5 "2023-02-28T03:20:07Z")

</div>

Hi Dave,

Unfortunately our DB Admin has no further information he can give me.

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [March 1, 2023, 5:09am UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/6 "2023-03-01T05:09:46Z")

</div>

Hi Bruce,

Although we have not managed to reproduce the issue that you are seeing, we have identified one area in the code where it is possible for a database session to cross threads. We have patched this code and you can download an update using the following links.

- [Download Continua CI Server v1.9.2.1083 (64 bit)](https://downloads.finalbuilder.com/downloads/continua/1.9.2/ContinuaCI.Server.Setup_x64_1.9.2.1083.exe)
- [Download Continua CI Agent v1.9.2.1083 (64 bit)](https://downloads.finalbuilder.com/downloads/continua/1.9.2/ContinuaCI.Agent.Setup_x64_1.9.2.1083.exe)
- [Download Continua CI Agent v1.9.2.1083 (32 bit)](https://downloads.finalbuilder.com/downloads/continua/1.9.2/ContinuaCI.Agent.Setup_1.9.2.1083.exe)

Please let us know if you see further uncommitted transactions after installing this version.

---

<div class="post-metadata">

**Author:** ![bruce\_at\_ds](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/b/3be4f8/32.png) [@bruce\_at\_ds](https://www.finalbuilder.com/forums/u/bruce_at_ds)\
**Post date:** [March 1, 2023, 11:03pm UTC](https://www.finalbuilder.com/forums/t/revisited-ms-sql-server-rcsi-and-continua-database/7334/7 "2023-03-01T23:03:50Z")

</div>

Hi Dave,

Thanks for that. I’ve installed v1.9.2.1083 this morning. We’ll let you know how it goes.

I’m about to go on leave for a few weeks, so you may not hear back straight away.

Regards,  
Bruce
