SourceGear Support

OK. Did you get a chance to run the queries w/ SHOWPLAN_ALL set to ON? I'm going to look at this again to see if I can find a way to improve performance, but I'm going to need a day or two to hash things out. In the mean time, if you could get the execution plan, I can see if a modification to the ...

OK. Did you get a chance to run the queries w/ SHOWPLAN_ALL set to ON? I'm going to look at this again to see if I can find a way to improve performance, but I'm going to need a day or two to hash things out. In the mean time, if you could get the execution plan, I can see if a modification to the ...

If the last statement is causing the 14-20 seconds, let's take a look at the execution plan for these statements: 1) Run - CREATE TABLE #tbltreerevfolders ( treelevel [int] NOT NULL, fullpathhash [binary](16) NOT NULL, parentpathhash [binary](16) NOT NULL, objid [bigint] NOT NULL, objverid [bigint]...

OK. This seemed to take 15 seconds. Is that correct? What happens if you remove the last SQL Statement -- REMOVE THIS FROM THE ENTIRE QUERY - SELECT DISTINCT lf.objid, lf.hostname, lf.locktype, lf.folderobjid, lf.lockwhen, lf.fullpath, lf.localpath, lf.comment, lf.miscinfo, lf.userid, lf.login, lf....

Valik: Sorry. I wasn't specific enough on my last post. Like the other queries, can you send me the messages output? At this point, the data is not important as the statistics from the query. I should note from examining the data, I'd like to recommend to people to only check out files they think t...

Valik: I have some personal stuff that needs my attention. I'll be away for a while. If you saw my last post, can you post the results? I'll check this out for any potential bottleneck later tonight. Thanks, Jeff, the results attached. I'm also going to sleep. It's quite late here in the Netherland...

It doesn't matter for this query, since we are directly accessing the database. However, it might not be a bad idea to turn it back on, so we don't forget later. With Folder Security turned OFF: SQL Server Execution Times: CPU time = 0 ms, elapsed time = 35 ms. SQL Server Execution Times: CPU time ...

Let's start at the beginning for checkout list security. Let's see how fast the current tree builds: SET STATISTICS TIME ON SET STATISTICS IO ON DECLARE @@currenttxid bigint SELECT @@currenttxid = currenttxid FROM sgvault.dbo.tblrepositories WHERE repid = 2 SELECT trf.treelevel, trf.fullpathhash, t...

This would explain things if determining security was the problem. Didn't you mention in an earlier post, when tested w/ Folder Security disabled from within the Admin Tool, the checkout updates were still taking 15+ seconds? Note - when disabling Folder Security, make sure to hit OK on the reposit...

OK... From your doc, it seems subsequent GetCheckoutListChanges are returning in the expected amount of time, so I don't think the problem is client related. Let's take a closer look at the checkout list table. Can you post ( or send to me in an email for more privacy ) the message output ( not the...

I did check with another machine. Using a backup and importing it in a different server where Vault and Sql Server are installed. No improvement encountered. I think we are getting confused with the MB, I mean a performance of 15 MBYTES per second which corresponds with your 150 MBITS per second No...

You mentioned you are using SQL Server. Within SQL Server's Enterprise Manager, there is a Maintenance Job Wizard. I would recommend looking at creating / running a maintenance job weekly. I did make a new job with the following specs: - Reorganize data and index pages (10%) - Check database integr...

We need some help, we are currently going from VSS to Vault for many reasons... Is it safe to assume the files were imported from VSS? Yes we deed. If so, have you run any database maintenance on the sgvault database? Things like updating the statistics, defragging indices, etc. Not that I'm aware ...

We need some help, we are currently going from VSS to Vault for many reasons and people are getting desperate because of the poor performance of Vault. We were using also SourceOffsite and were very happy in combination with VSS, but stability and performance (of VSS) were the main reasons to change...