Migrating SQL 2000 to 2005

[luther_miller]

I would like to upgrade the SQL 2000 Server on our Vault server to SQL 2005. I believe I can choose a SQL option to do an in place upgrade of the existing databases from 2000 to 2005.

If I do this, will Vault continue working as it does now? We are on 3.5.1 and plan to upgrade to 3.5.2 soon.

[Beth]

I haven't seen any problems with upgrading to SQL 2005, so you should be fine. Please remember to make a backup first anyway. Whatever Microsoft has for recommendations should be fine for us as well.

[Tri]

Can you please summarize a list of pros / cons of upgrading SQL Server 2000 to 2005?

And possibly post it as a new entry in the knowledge base section of the forum?

[luther_miller]

We performed the upgrade Friday morning and it took longer than we expected, but everything seems to be running fine. I just ran through the default setup wizard for SQL 2005.

I'm not sure if there are any benefits to Vauilt, but we wanted to have SSRS 2005 on that server with some other data and I did not want multiple instance of SQL Server running.

[Tri]

Thanks for your input, I would also be interested by SourceGear's recommendation or opinion regarding this topic.

[Beth]

There was one issue with SQL 2000 sp4 where repositories could not be deleted, but that issue isn't in sp3. Outside of that, the benefits you would receive would be what Microsoft lists as the benefits of going to SQL 2005. There are a few features that can't be done with Vault, such as replication and synchronization between multiple databases, but that is the same no matter which version you use.

Personally, I just like SQL 2005 better, but that's just more of a superficial aesthetics thing. We send to use it more here I believe, but you have to decide what's best for your organization.