1 database per repository

[bwhite]

Our database is over 98 GB which makes it more time consuming to backup and restore.

We feel like we are more at risk. If something happens to one repository
you can't restore just that one. All the repositories would have to be rolled back
and everyone loses recent changes, not just that team.

Is there any talk of adding the capability to store each repository in its
own database. We want to still be able to access all repositories from
the same UI as we switch between them frequently.

Thanks,
Brad.

[Beth]

There's a way to do this, but it would involve multiple instances of SQL and multiple web servers. Vault can only access one sgvault and sgmaster.

Do you backup daily? How much is lost if you have to ever roll back by one day?

Have you looked into transaction log backups?

So that I know what your environment is like, could you open a Vault GUI client, login, then go to Help - Technical Support and post the information from there? You don't need to include the licensing information at the bottom.

[bwhite]

> There's a way to do this, but it would involve multiple instances of SQL
> and multiple web servers. Vault can only access one sgvault and sgmaster.
I want it to be in a single UI, preferably with switching repositories just as
easy as it is now.

>
> Do you backup daily?
Snapshots, two times per day.

> How much is lost if you have to ever roll back by one day?
I don't want TeamA to be affected by problems with the TeamB
repository. It is one thing if I have to redo, reapply, all the changes
for "our" projects, but I want to minimize that impact as much as
possible, so that as few people as possible have to go back and
find what got lost.

>
> Have you looked into transaction log backups?
>
> So that I know what your environment is like, could you open a Vault GUI client,
Client Information
Vault Client Version: 5.0.4.18845
.Net Framework Version: 2.0.50727.4200
Operating System: Microsoft® Windows Server® 2008 Standard without Hyper-V
Service Pack: 2.0
OS Version: 6.0.6002
Total Physical Memory: 3 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Vault Server Version: 5.0.4.18845
.Net Framework Version: 2.0.50727.4200
Operating System: Microsoft® Windows Server® 2008 Standard without Hyper-V
Service Pack: 2.0
OS Version: 6.0.6002
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 6.0 <X86> (Build 6002: Service Pack 2) (VM)

HTH,
Brad.

[Beth]

I want it to be in a single UI, preferably with switching repositories just as
easy as it is now.

If you mean the client being able to easily connect, that's not a problem. A client can connect to different servers. For the client, it would be similar to connecting to our public demo server and then connecting back to your own server.

The server side though is what requires a lot of changes. You would need a separate SQL instance for each set of Vault databases, and you would need a separate machine or web server to host the server software for each install of the server software. If you have the hardware and SQL licenses to run multiple Vault servers though, then this is very feasible.

Snapshots, two times per day.

What are you using for those snapshots?

We have a feature request to allow separate backups of repositories that I can add your vote to.

One thing you could try is using our Export/Import tool to create archives of individual repositories. If your repositories are large, the Export/Import could take a long time though. Also, if you have ever used Obliterate, then there's a good chance that it won't export. Obliterate and Export/Import are not compatible. The Export/Import tool installs with the client, so anyone with the client and a login can try it. Using that you could export single projects or entire repositories.

What do you currently store in Vault? Are there a lot of videos and images or are you only storing text files? Do you store builds in Vault? Is there any redundant data?

[bwhite]

Beth wrote:
> Obliterate and Export/Import are not compatible.
Can I vote for that to be fixed?

Thanks,
Brad.

[bwhite]

Beth wrote:
> What are you using for those snapshots?
Arcserver D2D

HTH,
Brad.

[Beth]

I've recorded your vote on the request to change how exports and obliterates work together.

Have you used obliterate already? If not, then we can start discussing some reorganizing of your database to get the kind of separation that you want or to trim your database as you mentioned in the other thread.

F: 15381

[DeveloperPaul]

Does Vault support one database per repository as yet? This was a huge attraction to SourceSafe and something I really need in a source code control system.

I want to be able to keep each client's work together as a package. I frequenly will provide my clients with the latest copy of their projects including source code versions, and I'd like the code to be wrapped up in a source code control repository... combining all projects into the one database, or setting up multiple IIS and database instances are messy ways to work.

Thank you,

Paul.

[Beth]

Vault does not yet support multiple databases for one server to connect to, but you can have multiple repositories and place one client's data per repository. Then if a client wanted their entire repository, you could export it from Vault, sent them the export file and they could import it into their own Vault installation.

[DeveloperPaul]

Thank you Beth,

You mentioned that Vault doesn't currently support this capability. Is this functionality that is expected in a future release and, if so, when?

Regards,

Paul.

[Beth]

I have a feature request open that I will add your vote to, but I don't have any kind of timeline on it currently.

F: 11211