SQL Server 2005
(1)
SQL Server 2000
(1)
Database
(1)
Rtcconfig
(1)
Presence
(1)
Kb924604
(1)
Caveats
(1)
Cert
(1)

Upgrading LCS 2005 SP1 SQL Database from 2000 to 2005

Asked By shnerk
18-Nov-09 12:49 PM
Hello, I have been tasked with upgrading our LCS 2005 SP1 EE backend to SQL
2005 from SQL 2000.  I have found KB941317 which explains how to move LCS 2005
database from a computer running SQL Server 2000 to a computer that is
running SQL 2005 SP1.  I think I am ok with following that.  I also found the
information on KB911996, which is currently installed and how to deal with
that.

I still have questions, however, concerning archiving and certificates.  We
currently utilize archiving on our SQL 2000 server.  Can this database be
moved over, or should we start from scratch on the new SQL 2005 server?  We
also have a certificate issued from a separate server to allow MTLS.  Will a
new cert need to be created?  The front end server is not changing nor is the
pool name, just the database backend.

I am just trying to put all the steps together and hopefully finding all the
caveats involved before attempting this change.  Unfortunately we do not have
a test environment for LCS, so it is a one shot deal for me.

Does anyone know if I have missed any available documentation?  Is this
going to be easier than I am anticipating?  Any help would greatly be
appreciated!!!

"shnerk" wrote:

PF replied to shnerk
19-Nov-09 02:39 AM
"shnerk" wrote:

Hi shnerk,The only documentation I found was KB941317.

PF replied to shnerk
19-Nov-09 03:01 AM
Hi shnerk,

The only documentation I found was KB941317.

The archive database can be migrated in the same way as the rtc and
rtcconfig databases, but you need to deactivate then reactivate the archive
service against the new database once it is been moved.

Also I found that I needed to install the backwards compatibility module
from SQL 2005 on the archive server for the reactivation to complete.

And also be aware that the migrated databases will still run in "SQL 2000"
mode even when they have been migrated. You need to change the "Compatability
level" of each database to SQL Server 2005  - my DBA tells me this will
improve performance.

And if you are using Federation, you will need the hotfix from kb924604 to
get presence working again for federated contacts:

http://support.microsoft.com/kb/924604

HTH,

Garry

Thanks Gary. That does help and I think we are good to go now.

shnerk replied to PF
19-Nov-09 12:11 PM
Thanks Gary.  That does help and I think we are good to go now.
Post Question To EggHeadCafe