We have been running sql profiler against our database and noticed that the following query is being run every 1 to 2 seconds and lasts 1 to 2 seconds even if developers aren't connected.
Can you shed some light on what this is doing and how we can decrease the frequency? Thank alot.
Rodney
exec dbo.spqueryhistory @userid = 3, @repid = 1, @txid = 879, @objid = 20840, @objprops = 1, @fullpath = N'$/Projects30/sites/cda', @recursive = 1, @separator = N'/', @splitchar = N',', @itemtypelist = N'60,70,10,70,10,190,80,200,202,201,120,130,150,220,150,220,170,180,210,140,20,40,30,50,20,40,30,50,160,230', @begindate = 'Dec 9 2005 7:15:38:000PM', @enddate = 'Dec 9 2005 11:18:57:000PM', @sortlist = N'2147418115', @rowlimit = 0, @showlabels = 0
Slow Database Query
Moderator: SourceGear
I'm not all that familiar with your configuration, but something is asking the server for history on $/Projects30/sites/cda.
Vault itself will not do this. Do you have a scheduled Command Line Client task making the history query?
Or perhaps you are using a Continuous Integration product like CC.Net or Draco.Net?
If you want to track this down, you could place the Vault Server into Debug log mode, and then try to map up the history request in the log file to SQL Server's profiler. Then using that information, you should be able to find user account / machine where the request originated.
Vault itself will not do this. Do you have a scheduled Command Line Client task making the history query?
Or perhaps you are using a Continuous Integration product like CC.Net or Draco.Net?
If you want to track this down, you could place the Vault Server into Debug log mode, and then try to map up the history request in the log file to SQL Server's profiler. Then using that information, you should be able to find user account / machine where the request originated.
Jeff Clausius
SourceGear
SourceGear