SourceGear Support

Let's narrow things down a bit. Try: EXEC sgvault.dbo.spdeletecheckoutlists @repid = 2, @daysold = 5 Then re-try the get lock changes from above. Well just the spdeletecheckoutlists has taken 13 minutes so far and I'm not quite sure what's going on (should it take that long?). The sqlserver.exe pro...

Also, on the SQL maintenance routine. By default, all commands are commented out in my posting. Please verify that you have uncommented only one of the commands (UPDATE STATISTICS, DBCC DBREINDEX, or DBCC INDEXDEFRAG) Each one is done separately (so all reindex, then all update statistics, then all...

Let's narrow things down a bit. Try: EXEC sgvault.dbo.spdeletecheckoutlists @repid = 2, @daysold = 5 Then re-try the get lock changes from above. Well just the spdeletecheckoutlists has taken 13 minutes so far and I'm not quite sure what's going on (should it take that long?). The sqlserver.exe pro...

OK. Run this query: SELECT repid, name FROM sgvault.dbo.tblrepositories, Now, using the repid from above (I used 2) in my sample: DECLARE @repid [int], @colistid [bigint]; SET @repid = 2; SELECT @colistid = currentcolistid FROM sgvault.dbo.tblrepositories WHERE repid = @repid; exec sgvault.dbo.spge...

Ran the update statistics, only took a few seconds (19 actually). The second command finished in <1 second.

Yes I can manually kill the processes which I've done already (had to to get the Vault server to respond to even a login), but the exact same set of repro (checkin/checkout/undo checkout) causes the blockage again (every time and on any single file or folder).

Do you know what command was run? Yes, it's your suggested script for defragging, reindexing and updating statistics in your KB. DBCC REINDEX, UPDATE STATISTICS, DBCC INDEXDEFRAG. However, if you're not comfortable with Vault 3.1, then at least get up to Vault 3.0.7 so you do not encounter the race...

The server has a nightly maintenance schedule that updates the vault database. The last log file I received for it (last night at 1am) reported everything in tip top shape. So you suggest a beta version? What will that do to the database? What if the beta version is worse? Can I revert back to an ea...

Hm, looking at Vault 3.0.7, I see this:

Server Only
· Allow better concurrency on refresh and checkout commands

Maybe I should try 3.0.7 first?

If this helps any:
Windows 2003
Vault 3.0.6

By "the entire server stops responding" I really meant "users can no longer get latest, etc as they get blocked whenever Vault tries to refresh the repository info.

Also, I turned folder security off to see if that would have any affect (and it didn't, but it's still off).

So this started some time over the weekend... People came in this morning and all of a sudden the Vault server can't retrieve the repository structure from the server. Anyway, I've basically narrowed it down: I clean the server (restart SQL, restart IIS, etc) and connect and login and get a normal s...

Also, on this same wizard, what would be the chance of getting the merging, etc to be done on a non-UI thread. Right now I have to sit and watch the merge UI lock up for minutes while it's doing the work in the "background". A lot of users will kill an application upon its UI locking up. L...

I have a dual monitor setup, and I've been doing a lot of merging lately and the merge wizard will only ever start on the primary monitor and not the monitor the Vault GUI is actually on. I assume this is just the form not being set to CenterParent for its start position.

So that worked, but couldn't Vault have been a little smarter here? Something like "your baseline file can't be found, Vault needs to create a new baseline file blah blah blah" and just do a get latest and create a new baseline file? The file that was failing only had a single version and ...