SourceGear Support

Yes, we restored the SQL backup files from the old server to SQL S016 in the new server. When you do that, SQL Server leaves the compatibility level as per the backup file (i.e., as it was on our old server). Our question is: Has Vault (the stored procedures, etc.) been tested with and validated to ...

We just moved our Vault database to a new server, running SQL 2016. Everything went fine with the move, but we noticed that the Compatibility Level for all the Vault databases is set to SQL Server 2008 (level 100). Is there a reason for this? Is it safe/advisable to move it to SQL Server 2016 (level...

I've studied the instructions in the KB about moving Vault databases, but we want to move the databases to the Azure SQL Service. You can't backup/restore or attach/detach with that service; instead, you have to use the SSMS task "Deploy database to Azure SQL database". Would the instructi...

Ah, thank you. We can use SQL authentication. This is not a new installation; we already have Vault running on machine A, and we want to move just the databases to machine B. There's a FAQ detailing which databases to move, which is clear; but is there a simple way to reconfigure Vault to point to t...

Is it possible to have the actual Vault database on a separate server from that hosting the Vault Web application?

That is:
Machine A (Web server only) hosts Vault server application
Machine B (SQL Server only) hosts Vault databases

If so, how is that set up?

Thanks

Has anyone at all been able to get source control to appear and work in SSMS 17?

I've followed the instructions in the links in the posts above, but they do absolutely nothing.

Does SourceGear plan to address this major gap with an add-in?

Thanks,

C17