session lock table growth out of control
Josh Kewley <[email protected]> Tue, 20 Apr 2004 21:30:49 -0700
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <A20522F0-041E-460C-80EC-59E900AB96B3@mimectl> |
--_BE0E8351-EC4E-4CD1-8F14-339424885689_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, With only a handful of developers working on our Vault server, we are runni= ng into a problem where hundreds of thousands of rows in the session lock t= able (tblsessionrellocks) are being created upon check-in that are not bein= g deleted. This causes the size of our database to grow by gigabytes each w= eek, and causes Vault to operate very, very slowly. I have seen mention of = this problem with past versions of Vault, but apparently it was something t= hat was fixed in recent versions. (http://support.sourcegear.com/viewtopic.= php?t=3D285). Our hack to keep productive in the meantime has been to delet= e all records from this table when vault is not being used.=20 We started with the 1.x version, and have been following the upgrade paths = (without incident) to the current version that we run (2.0.2). We are runni= ng both our SQL server and web server on Windows Server 2003. We notice the= same problem with the vault client, as well as with the VS.Net IDE. We do = a lot of massive check-ins after generating base libraries, which is when t= he server really gets beat up. Assistance is appreciated. -Josh --_BE0E8351-EC4E-4CD1-8F14-339424885689_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <HTML dir=3Dltr><HEAD></HEAD> <BODY> <DIV><FONT face=3DArial color=3D#000000 size=3D2>Hello,</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>With only a handful of developers working = on our Vault server, we are running into a problem where hundreds= of thousands of rows in the session lock table (tblsessionrelloc= ks) are being created upon check-in that are not being deleted. This causes= the size of our database to grow by gigabytes each week, and causes Vault = to operate very, very slowly. I have seen mention of this problem with past= versions of Vault, but apparently it was something that was fixed in recen= t versions. (<A href=3D"http://support.sourcegear.com/viewtopic.php?t=3D285= " target=3D_blank>http://support.sourcegear.com/viewtopic.php?t=3D285</A>).= Our hack to keep productive in the meantime has been to delete all re= cords from this table when vault is not being used. </FONT><= /DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>We started with the 1.x version, and have = been following the upgrade paths (without incident) to the current ver= sion that we run (2.0.2). We are running both our SQL server and web server= on Windows Server 2003. We notice the same problem with the vault cli= ent, as well as with the VS.Net IDE. We do a lot of massive check-ins after= generating base libraries, which is when the server really gets beat up.</= FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Assistance is appreciated.</FONT></DIV> <DIV><FONT face=3DArial size=3D2>-Josh</FONT></DIV></BODY></HTML> --_BE0E8351-EC4E-4CD1-8F14-339424885689_--