Technical Questions about Vault implementation

[Samuel Jack]

Hello,
Do you mind if I ask some technical questions to do with the implementation of Vault?

For example, in 2.0.5, what logging framework are you using? log4net, built in .Net Trace classes, or one of your own making?

What are your experiences with storing large binary files in SQL Server 2000 (presuming that's how you do it)? Are there any performance issues, or other problems? Benefits?

Hope I'm not being too cheeky!

Sam

[Samuel Jack]

Sorry, this should really have been posted to the Discussion forum.

[jclausius]

Samuel:

Do you mind if I move this to the discussion forum?

[Samuel Jack]

Not at all: go ahead!

Sam

[Samuel Jack]

Not at all: go ahead!

Sam

[jclausius]

Hello, Do you mind if I ask some technical questions to do with the implementation of Vault?

For example, in 2.0.5, what logging framework are you using? log4net, built in .Net Trace classes, or one of your own making?

Vault uses its own logging mechanism. The log settings are controlled by the Admin Tool.

What are your experiences with storing large binary files in SQL Server 2000 (presuming that's how you do it)? Are there any performance issues, or other problems? Benefits?

Our overall experience has been very good. In my opinion, it was well worth the choice of storing the files in the database. The benefits of an entirely self contained system lightens the burden for maintenance of the database / disk(s).

Of course, the alternative of storing files on disk would be much faster, but since, on average, the changes (deltas) to files are not that large, the impact is less noticeable.

Plus it doesn't hurt that Microsoft is supposedly making improvements in this area for future versions of SQL Server.

Hope I'm not being too cheeky!Sam

Not at all. Its why the forum is here.