Upgrading from 2.0.6 to 3.5 - database is SQL Server 2005

[mbrit]

Hi,

Apologies for the lack of info on this post - I'm posting this now just to get a straight answer about this.

We have Vault 2.0.6 running SQL Server 2005. It was originally installed on 2000, but we upgraded the server.

We are now trying to upgrade the database to Vault 3.5. Should this work?

Matthew

[lbauer]

Vault 2.0.6 did not support SQL Server 2005, so there *might* be a problem with the database.

NOTE: if you install the .NET Framework 2.0 on a machine with Vault 2.0.6 Server, accessing a repository will corrupt it beyond repair, because of a change in the way .NET 2.0 handles time.

I'd suggest first backing up the database, then running the 3.5 Vault Server installer over the current installation

If that fails, the best bet is to uninstall Vault 2.0.6, then restore a copy of the database prior to upgrading to SQL Server 2005, and install Vault 3.5. The install will upgrade the 2.0.6 database.

[mbrit]

Um - are you sure about this? We've had .NET 2.0 on the same box for the past four months and haven't noticed a problem - although we did choose to upgrade Vault because we were experience some weirdness.

What would the symptoms of this problem be?

Matthew

[mbrit]

Also - we upgraded our SQL Server box to 2005 about six months ago, so we can't restore from that far back as that's going to be pretty useless.

[lbauer]

Even though the NET 2.0 Framework is installed, the Vault Server may be using using .NET 1.1. Here's a KB article with details of the issue:
http://support.sourcegear.com/viewtopic.php?p=5841

Since you haven't had a problem with SQL Server 2005, I'd suggest trying the upgrade from 2.0.6 to 3.5. Back up your database first.

[mbrit]

Sorry - I'm a little unclear about my original question then...

Is it the case that upgrading from Vault 2.0.6 running on SQL Server 2005 to Vault 3.5 should work OK?

Cheers,
Matthew

[lbauer]

Yes, it should.