Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Migrating from SQL Server 2000 to 2005

8 views
Skip to first unread message

Rob Evans

unread,
Jul 28, 2008, 10:11:33 PM7/28/08
to
We currently have StarTeam Server 2005R2 running on Windows Server
2000 with SQL Server 2000.
We have tested the upgrade to StarTeam Server 2006 running on Windows
Server 2003 still with SQL Server 2000.
And, we are looking at the task of migrating that to SQL Server 2005.
Once we have that in place, we can then test out the further upgrade
to StarTeam Server 2008 - but we don't want to go there just yet.

I have the following Borland Support Knowledge Base articles:
KB 29239 - How to migrate from MSSQL Server 2000 to MSSQL Server 2005
KB 31003 - What is the upgrade path to get from my version to the
StarTeam 2008?

Both these articles only talk in detail about the StarTeam side of
things. In fact, the second of those articles says:
"Of course, this depends on your database version and being able to
successfully convert your database to a new version of Oracle or SQL
Server. Please consult with your DBA for that information."

Unfortunately, in our small environment, I have to act as the DBA. So,
I am looking for help with the SQL side of migrating from SQL Server
2000 to SQL Server 2005.

Has anyone done this already? And, can you give some helpful advice?
Does it involve setting up a new database, or is that done by the
Migrate process? What has to be done in ODBC? Can it be done on one
machine or should it be done on two?

And, when the first of the above articles says: "Create a new server
configuration that points to MSSQL 2005", what does that mean for the
StarTeam configuration XML file? Is it just a matter of copying the
old config, pasting it in and modifying some parameters?

--

Regards, Rob Evans

Rob Evans

unread,
Aug 1, 2008, 11:42:16 PM8/1/08
to
I have discovered that the Migrate process handles all the details
itself through the dialogue.
It creates the database and ODBC entries as well as the new database,
based on user input.
The whole process is quite straight-forward - though the migrate
itself can take several hours.
Regards, Rob E.

"Rob Evans" <ro...@fast.fujitsu.com.au> wrote in message
news:488e7c53$1...@newsgroups.borland.com...

0 new messages