Best way to move an entire repository to another database?

[robe070]

Hi,

Could you tell us what the steps are to move an entire repository out to another SQL Server instance so that the original database performs as if that removed repository never existed?

thanks

[robe070]

...and can the 2nd instance be on the same SQL Server?

Is there anything to beware of? IIS?

How do you refer to the 2nd instance from the Client? - its usually the machine name.

[Beth]

You can have the second SQL instance be on the same server. The Vault connection needs machine name\instance name, or just the machine name for the default instance if it's not named.

You can move the repository by one of two methods.
1) Use our Export/Import tool to export everything out and import it to the new Vault server.
2) Restore a backup of the entire database to a SQL Server (or instance), then install a 2nd Vault server to pick up that restored database. Next delete all but the one repository from the new install, and on the old install, delete the repository you kept on the second install.

[robe070]

Thanks Beth.

And will the original database be as if the deleted repository had never been there? Like indexes, or deleted objects, or...?

[Beth]

A repository delete removes all traces of that repository.

You will still want to run the recommended SQL maintenance such as updating statistics and reindexing that is mentioned here: http://support.sourcegear.com/viewtopic.php?t=2924. It's not required after a delete, but since you mentioned performance in another post, I'm assuming that's why you are removing a repository, and the SQL maintenance will help that.

[robe070]

since you mentioned performance in another post, I'm assuming that's why you are removing a repository, and the SQL maintenance will help that.

Thats correct. But the user capitulated late yesterday and is now going to remove all the binary objects that were coincident with slower performance in Vault. So for the moment we will not be moving the Repository.

[robe070]

You can move the repository by one of two methods.
1) Use our Export/Import tool to export everything out and import it to the new Vault server.
2) Restore a backup of the entire database to a SQL Server (or instance), then install a 2nd Vault server to pick up that restored database. Next delete all but the one repository from the new install, and on the old install, delete the repository you kept on the second install.

So, if we are going to move the repository we had better not obliterate if we are going to use option (1). But that is what we are planning on doing as the objects should not be in a source control repository, IMHO. So if we need to move the repository we will only be able to use option(2). Thats a bit messy with such a large repository (18 GB)

[Beth]

Obliterate often makes Export/Import unusable in the repository you obliterated in. It's best to use Export/Import first and then obliterate after if you still need obliterate at that point.