Vault Issues ith Version 3.16

[btd]

We are currently on Vault 3.16 (3659) SG. With this version we have the following (see below) issues. Does your latest version (???) address these issues?

1. Current version does not allow us to move folders/code/history from one repository child directory to a different or new folder within the same repository. In other words, there is no drag and drop capability. We want the ability to move folders and their files/history from one subsirectory in Vault to another AND keeping the history. Is this possible with the latest version?

2. Can Vault be migrated to SQLServer 2005 SP2 database?

3. Have there been any improvements in repository Obliterate? For example, our vault database is now over 16 GIG! When we use the Admin tool and select Obliterate, the "Deleted items" that appears can't be sorted or organized and it does not package the files up by label. The UI is weak with only a few columns and no sorting or categorization (ie. by version).

4. Security. We've had some wierd things happen in Vault that we believe is a security hole! When ever we add a new user to Vault and assign him rights to various repositories, other existing users are granted repository access for different projects. I know this sounds far fetched, but its true. And it happens alot! So we were wondering if this has been reported and if its beed addressed/fixed with the latest (???) version.

Thanks

btd


PS What is the latest version of vault for SQLServer 2000?

[lbauer]

Vault Folder Export\Import was implemented in Vault 3.5.x. This allows you to move folders from one repository to another through an export process.

Vault 3.1 does support SQL Server 2005, though we haven't tested it with SP 2. You can restore the Vault database to a SQL Server 2005 machine or SQL Server instance, then reinstall Vault.

Vault 4.0.6 has a folder-by-folder view of items to be obliterated, which makes it easier to find items you want to obliterate. But the obliterate operation still takes a lot of time. We'd rather be accurate than fast.

I couldn't find any specific bugs logged that described the security issue you've been experiencing. We've made a number of fixes in Vault 4.x, so it's possible this was addressed, or it's also possible it's something specific to your configuration. Have you reported this to us before?

Regarding your last question -- All versions of Vault released to date will work with SQL Server 2000.

[btd]

Thanks for your quick reply. I have a few more questions.

What is the latest version of Vault that I can download, given my license agreement?

When did Vault (date and version) begin supporting SQLServer 2005?

Thanks

btd

[lbauer]

If you don't have maintenance or Gold support, Vault 3.1.9 is the latest free version for you.

Support for SQL Server 2005 came in July 2005, with the release of Vault 3.1.

[GregM]

There's no drag and drop, but there is a move function in the file menu for moving within the same repository.

[btd]

Since I do have support, waht's the latest version of Vault?

[lbauer]

Greg's right -- I misread your post. I thought you wanted to move folders to a different repository. Vault 3.1.6 has a Move function under the File menu. It wasn't added to the context menu until later.

If you have Gold Support, you can upgrade to the latest version 4.0.6. Vault 4.1 is currently out in Beta, but we don't have a specific release date to announce yet.