What should the Compatibility Level be set at?

If you are having a problem using Vault, post a message here.
Post Reply
c17
Posts: 6
Joined: Wed Jan 23, 2019 5:43 pm

What should the Compatibility Level be set at?

Post by c17 » Wed Feb 19, 2020 12:10 pm

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 130)?

Thanks

Tonya
Posts: 667
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: What should the Compatibility Level be set at?

Post by Tonya » Wed Feb 19, 2020 12:47 pm

Hello,

According the this Microsoft page, SQL Server 2016 is compatible with 130, 120, 110, 100:

https://docs.microsoft.com/en-us/sql/t- ... rver-ver15

I'm not sure why the value didn't change. Did you restore the databases on the new SQL Server machine during the move?

Thanks,

Tonya

c17
Posts: 6
Joined: Wed Jan 23, 2019 5:43 pm

Re: What should the Compatibility Level be set at?

Post by c17 » Wed Feb 19, 2020 1:00 pm

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 work with compatibility level 2016?

Thanks

Tonya
Posts: 667
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: What should the Compatibility Level be set at?

Post by Tonya » Wed Feb 19, 2020 1:03 pm

Hello again,

Yes, I can confirm that Vault version 10.x has been tested and is fully supported on SQL Server 2016. I have copied below a link to the Vault Compatibility Chart:

https://www.sourcegear.com/vault/docume ... chart.html

Tonya

Post Reply