Re: Side-by-side upgrade - moving master, msdb and model



Hello Rodney,

Yes, that´s what I thought.

So what I have to do here is to configure everything manually then ?

What does the statement below mean then - found on page 105 in the
"SQL2005UpgradeTechRef.doc" ?

"In some cases, you may want to copy the system databases, including the
master database, from the source SQL Server 2000 instance to the SQL
Server
2005 instance before transferring user databases. See the topic "Moving
System Databases" in SQL Server 2005 Books Online to see how to do this"

/Johnny

"Rodney R. Fournier [MVP]" wrote:

System databases on SQL 2000 are very different from system databases on SQL
2005. You can't just move then, though I am sure Geoff or one of the other
SQL MVPs will have a great work around or something.

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


"Johnny Lundgren" <JohnnyLundgren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:2472D1A7-D1A8-4779-A630-E088822CFBCD@xxxxxxxxxxxxxxxx
Hello,

I am soon performing a side-by-side upgrade on completely new hardware.

The old stand-alone server has a 32-bit SQL 2000 Standard Edition SP3a
installed.
I want to move all databases to a 64-bit SQL 2005 Standard (SP2 - when it
is
released) clustered installation on the new hardware.

My question:

I want to move not only the user databases but also MASTER, MSDB, MODEL
databases to avoid having to recreate and configure logins, maintenance
jobs
etc.

Is this really possible ?

On page 105 in the "SQL2005UpgradeTechRef.doc" the following statement is
found:

"In some cases, you may want to copy the system databases, including the
master database, from the source SQL Server 2000 instance to the SQL
Server
2005 instance before transferring user databases. See the topic "Moving
System Databases" in SQL Server 2005 Books Online to see how to do this"

When checking the Books Online, I get the impression that moving MASTER,
MODEL and MSDB only applies when moving between two SQL 2005
installations.
Not from SQL 2000 to SQL 2005.

Can anyone clear this out for me ?

Regards

Johnny Lundgren




.



Relevant Pages

  • Re: Side-by-side upgrade - moving master, msdb and model
    ... MVP - Windows Server - Clustering ... "In some cases, you may want to copy the system databases, including ... from the source SQL Server 2000 instance to the SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: active/passive cluster vs log shipping
    ... So assuming I could remote in, what other benefits do clustering provide me ... over log shipping? ... > Columnist, SQL Server Professional ...
    (microsoft.public.sqlserver.clustering)
  • Re: Create SQL cluster on 2003
    ... Since you are in a cluster configuration, ... Microsoft SQL Server MVP ... We only about about 20 databases - all ... Move Databases Between Computers That Are Running SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: MSCS Questions
    ... There is little effect on performance one way or the other with clustering ... If Sql Server can not take advantage of more memory then having too ... Andrew J. Kelly SQL MVP ...
    (microsoft.public.sqlserver.server)
  • Re: Help!! Trying to migrate data from one SQL to another?!?
    ... I came up to the window on the DTS Wizard which has the option to ... I can defend myself on PL/SQL but I am not much of a SQL Server ... The application performs a replication between databases but due to ...
    (microsoft.public.sqlserver.dts)

Loading