Hi,
I'm not sure if this is a bug or if Vault is supposed to operate like this, but I've noticed that Vault keeps 17 open connections to the database server.
Most of the time these connections are idle.
Its not a big deal, but it would be nice if Vault didn't keep so many connections around.
I'm using SSPI and a domain account for Vault to connect to my database server.
Thanks
Andy
Sql Server connections
Moderator: SourceGear
The Vault Server uses the .Net Framework connection for SQL Server connectivity. The default is set to use connection pooling for performance reasons.
If you want the pool's connection length changed, take a look at the Connection Lifetime=X, where X is a value in seconds, in the server's web.config file for this setting.
See Connection Pooling for the .NET Framework Data Provider for SQL Server for additional information about the the SQL Server connection.
If you want the pool's connection length changed, take a look at the Connection Lifetime=X, where X is a value in seconds, in the server's web.config file for this setting.
See Connection Pooling for the .NET Framework Data Provider for SQL Server for additional information about the the SQL Server connection.
Jeff Clausius
SourceGear
SourceGear