Show history taking a long time or not working

MapData · Post by **MapData** » Thu Aug 23, 2007 5:46 pm

One of the users of vault here are reporting since an upgrade to version 4.0.2 show history has been slow or not working.

I tryed it with a few of our projects in vault and the ones that are small and havent been changed much are working ok but the one that are larger or have been changed quit a bit arent working

from the server log:
----24/08/2007 9:20:12 AM admin--mapdata18.mapds.com.au(192.168.10.28)--SSL Disabled BeginHistoryQuery returned: FailDBFault
----24/08/2007 9:21:23 AM admin--mapdata18.mapds.com.au(192.168.10.28)--SSL Disabled System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.QueryHistory(VaultSqlConn conn, Int32 nUserID, Int32 nRowLimit, Int64 nTxID, VaultHistoryQueryRequest hqr, SqlDataReader& dr) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.QueryHistory(VaultSqlConn conn, Int32 nUserID, Int32 nRowLimit, Int64 nTxID, VaultHistoryQueryRequest hqr, SqlDataReader& dr)
----24/08/2007 9:21:23 AM admin--mapdata18.mapds.com.au(192.168.10.28)--SSL Disabled BeginHistoryQuery returned: FailDBFault

client gui error message:
A database error has occured (FailDBFault)

lbauer · Post by **lbauer** » Fri Aug 24, 2007 6:18 am

It looks like SQL Server is timing out. You could adjust the SQL Server timeout value, to see if that helps.

This setting is in the Vault.config file in the VaultService directory.

Look for this line:

<SqlCommandTimeout>360</SqlCommandTimeout>

Change the number to something larger, like 3600 or even 7200, and then restart your Vault server (iisreset.exe)

MapData · Post by **MapData** » Sun Aug 26, 2007 11:08 pm

lbauer wrote:Change the number to something larger, like 3600 or even 7200, and then restart your Vault server (iisreset.exe)

Wouldnt that set the time out to 1 hour? Im trying to decrease the time it takes for show history to show history not just wait longer for it. (sorry if that sounds bitchy its only ment to be a statment of what Im trying to do)

Even the 6 min timeout at the moment is to long to wait and our users are complaining its taking to long.

Isnt there something that can be done on the database or in vaults settings itself that could speed this up? If not how do I downgrade to version 4.0.1?

lbauer · Post by **lbauer** » Tue Aug 28, 2007 3:25 pm

Changing the setting will at least keep SQL Server from timing out.

We didn't make any code changes to Show History in Vault 4.0.2, so it's not clear why it's taking longer for you than it did in 4.0.1.

Do all history operations take a long time, or just on items with hundreds of versions?

Is there anything in the Vault Server log that corresponds to the slowdown of History?

MapData · Post by **MapData** » Tue Aug 28, 2007 5:17 pm

We didn't make any code changes to Show History in Vault 4.0.2, so it's not clear why it's taking longer for you than it did in 4.0.1

Ok, scratch that idea

Ive changed the time out to 10 mins and its not timing out any more.

Its only with projects that have a large amount of history. (The one I was looking at that was timing out before had 'Showing 1000 items (truncated)' on the bottom of the form)

There's nothing out of the ordinary in the logs.

Clearing the vault client cache wouldnt help would it?
Is there a show history function in the web client?

Thanks for the assistance

lbauer · Post by **lbauer** » Thu Aug 30, 2007 7:56 am

I don't think clearing the client-side cache would help. You can see individual file versions in the web client, but not folder versions, branches, labels, etc.

If you show history using a Vault GUI Client on the Vault Server machine, connecting to the Vault Server using localhost as the server name, is history still as slow?

lbauer · Post by **lbauer** » Thu Aug 30, 2007 11:56 am

Another thought -- do you do regular SQL Server maintenance? That might help performance:
http://support.sourcegear.com/viewtopic.php?t=2924

MapData · Post by **MapData** » Thu Aug 30, 2007 4:51 pm

Still takes a long time to show history on the server using local host.

We do some but I will take a look at anything else we can do and get back to you.

Thanks for the help